Return-Path: postman 
Delivery-Date: Tue, 26 Oct 93 15:01:16 PDT
Return-Path: postman
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA01600; Tue, 26 Oct 93 14:55:55 -0700
Resent-From: postman (POSTGRES mailing list)
Resent-Message-Id: <9310262155.AA01600@postgres.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: scottk@utig.ig.utexas.edu
Received: from utig.ig.utexas.edu by postgres.Berkeley.EDU (5.61/1.29)
	id AA01592; Tue, 26 Oct 93 14:55:46 -0700
Received: from rimu.ig.utexas.edu.utig by utig.ig.utexas.edu (4.1/SMI-4.1)
	id AA18052; Tue, 26 Oct 93 16:53:32 CDT
Date: Tue, 26 Oct 93 16:53:32 CDT
From: scottk@utig.ig.utexas.edu (Scott Kempf)
Message-Id: <9310262153.AA18052@utig.ig.utexas.edu>
To: postgres@postgres.berkeley.edu
Subject: Minor bug.
Resent-To: postgres-dist
Resent-Date: Tue, 26 Oct 93 14:55:53 PDT

Dear Postgurus,

Sorry if this is mailed to the wrong place.  Last time I set mail
here I thought it would go out on the list, instead I just got a
responce saying someone may look into my problem.   This time that's
all I want.

Palloc() in the fe-pqstubs.c part of libpq doesn't check the
return value from malloc().  When memory runs out, bing,
segmentation violation.

The code:

/* ----------------
 *      palloc (frontend version)
 *      pfree (frontend version)
 * ----------------
 */
Pointer
palloc(size)
    Size size;
{
    Pointer p;
 
    p = malloc(size);
    bzero(p, size);
 
    return (p);
}


Also in the same file, it would be nice if elog() did something closer
to the elog() in the backend.  I have user defined types which call
elog() when there is trouble.  Since the code is used both in the front
end and the back end a better front end elog() is needed.

Luckly with postgres we get source, so don't worry about me.  I fixed
my version.  I just thought this would be helpful for the next release.

				Thanks much,
				Scott
