Re: pgsql/src/backend/postmaster (postmaster.c) - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql/src/backend/postmaster (postmaster.c)
Date
Msg-id 19451.962637374@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql/src/backend/postmaster (postmaster.c)  (eisentrp@csis.gvsu.edu)
Responses Re: pgsql/src/backend/postmaster (postmaster.c)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-committers
eisentrp@csis.gvsu.edu writes:
>> ... Seems like the correct fix
>> is that guc.c ought to be handling this logic, not postmaster.c.
>> Peter, what do you think?

> I concur.

OK, do you want to fix it, or shall I?

BTW, it is now possible for guc.c to use palloc in TopMemoryContext,
if you want to do that.  There's no real functional difference between
that and malloc --- except that MemoryContextStats() could include
the space used by guc.c --- but if it's just irritating you to use
malloc then you could change it.

            regards, tom lane

pgsql-committers by date:

Previous
From: eisentrp@csis.gvsu.edu
Date:
Subject: Re: pgsql/src/backend/postmaster (postmaster.c)
Next
From: Bruce Momjian - CVS
Date:
Subject: pgsql/doc/src/sgml (func.sgml)