| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2004-06-24 16:55:42 | Re: bug in GUC |
| Previous Message | Thomas Hallgren | 2004-06-24 14:45:31 | Re: bug in GUC |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-06-24 16:34:05 | Re: 7.5-dev, pg_dumpall, dollarquoting |
| Previous Message | Tom Lane | 2004-06-24 15:53:45 | Re: Fixing pg_dump |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2004-06-24 16:55:42 | Re: bug in GUC |
| Previous Message | Thomas Hallgren | 2004-06-24 14:45:31 | Re: bug in GUC |