Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] bug in GUC

From: James Robinson <jlrobins(at)socialserve(dot)com>
To: "Thomas Hallgren" <thhal(at)mailblocks(dot)com>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>,pgsql-docs(at)postgresql(dot)org
Subject: Re: [HACKERS] bug in GUC
Date: 2004-06-24 15:59:59
Message-ID: 8B33FE4F-C5F7-11D8-8247-000A9566A412@socialserve.com (view raw or flat)
Thread:
Lists: pgsql-docspgsql-hackerspgsql-patches
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


In response to

pgsql-docs by date

Next:From: Alvaro HerreraDate: 2004-06-24 16:55:42
Subject: Re: bug in GUC
Previous:From: Thomas HallgrenDate: 2004-06-24 14:45:31
Subject: Re: bug in GUC

pgsql-hackers by date

Next:From: Josh BerkusDate: 2004-06-24 16:34:05
Subject: Re: 7.5-dev, pg_dumpall, dollarquoting
Previous:From: Tom LaneDate: 2004-06-24 15:53:45
Subject: Re: Fixing pg_dump

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2004-06-24 16:55:42
Subject: Re: bug in GUC
Previous:From: Thomas HallgrenDate: 2004-06-24 14:45:31
Subject: Re: bug in GUC

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group