"Thomas Hallgren" <thhal(at)mailblocks(dot)com> writes:
> Rather than clutter the code with the same ereport over and over again (I
> count 12 malloc's in guc.c alone), I'd like something like this:

The larger question is why it contains even one.  In general, use of
malloc in the backend is the mark of a newbie.  I'd think palloc in
TopMemoryContext would be a more suitable approach.

			regards, tom lane

In response to

• Re: bug in GUC at 2004-06-24 09:06:25 from Thomas Hallgren

Responses

• Re: bug in GUC at 2004-06-24 14:45:31 from Thomas Hallgren

pgsql-docs by date

Next:	From: Thomas Hallgren	Date: 2004-06-24 14:45:31
	Subject: Re: bug in GUC
Previous:	From: Thomas Hallgren	Date: 2004-06-24 09:06:25
	Subject: Re: bug in GUC

pgsql-hackers by date

Next:	From: Jeroen T. Vermeulen	Date: 2004-06-24 14:09:37
	Subject: Re: PREPARE and transactions
Previous:	From: Greg Stark	Date: 2004-06-24 12:54:09
	Subject: Re: warning missing

pgsql-patches by date

Next:	From: Tom Lane	Date: 2004-06-24 14:32:21
	Subject: Re: pg_dump --clean w/ <= 7.2 server
Previous:	From: Christopher Kings-Lynne	Date: 2004-06-24 13:58:22
	Subject: Re: pg_dump --clean w/ <= 7.2 server