public inbox for [email protected]  

help / color / mirror / Atom feed

From: James Robinson <[email protected]>
To: Thomas Hallgren <[email protected]>
Cc: PostgreSQL Development <[email protected]>
Cc: [email protected]
Subject: Re: [HACKERS] bug in GUC
Date: Thu, 24 Jun 2004 11:59:59 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>


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

view thread (10+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: [HACKERS] bug in GUC
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox