X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 11F6AD1B7CF;
	Thu, 24 Jun 2004 13:00:17 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 48615-06; Thu, 24 Jun 2004 16:00:09 +0000 (GMT)
Received: from mail.socialserve.com (office.socialserve.com [208.60.89.34])
	by svr1.postgresql.org (Postfix) with ESMTP id 2C264D1B199;
	Thu, 24 Jun 2004 13:00:06 -0300 (ADT)
Received: from localhost (localhost [127.0.0.1])
	by mail.socialserve.com (Postfix) with ESMTP
	id 4515F9953; Thu, 24 Jun 2004 12:00:06 -0400 (EDT)
Received: from mail.socialserve.com ([127.0.0.1])
	by localhost (ms2 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 25055-08; Thu, 24 Jun 2004 12:00:00 -0400 (EDT)
Received: from [10.1.1.94] (dynamic-94.socialserve.com [10.1.1.94])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by mail.socialserve.com (Postfix) with ESMTP
	id 2DE4B99D6; Thu, 24 Jun 2004 12:00:00 -0400 (EDT)
In-Reply-To: <cbeplq$2nl6$1@news.hub.org>
References: <20040624052712.GA7158@dcc.uchile.cl> <cbe5q2$kpa$1@news.hub.org>
	<13534.1088085728@sss.pgh.pa.us> <cbeplq$2nl6$1@news.hub.org>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <8B33FE4F-C5F7-11D8-8247-000A9566A412@socialserve.com>
Content-Transfer-Encoding: 7bit
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>,
	pgsql-docs@postgresql.org
From: James Robinson <jlrobins@socialserve.com>
Subject: Re: [HACKERS] bug in GUC
Date: Thu, 24 Jun 2004 11:59:59 -0400
To: "Thomas Hallgren" <thhal@mailblocks.com>
X-Mailer: Apple Mail (2.618)
X-Virus-Scanned: by amavisd-new at socialserve.com
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200406/9
X-Sequence-Number: 2407


On Jun 24, 2004, at 10:45 AM, Thomas Hallgren wrote:

> So, what you are saying is that there's no need for the functions I
> suggested and that a palloc using the TopMemoryContext will guarantee
> correct behavior on "out of memory"?

Perhaps a section regarding proper memory management code in the 
backend could be written , say, somewhere in the internals document 
around the coding conventions chapter:

	http://developer.postgresql.org/docs/postgres/source.html

I myself don't have a clue, not being a backend hacker, so I'll just 
slink back to my cave.

----
James Robinson
Socialserve.com