>> ... 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
In response to
pgsql-hackers by date
|Next:||From: Michael J Schout||Date: 2000-07-03 16:02:28|
|Subject: Strange "NOTICE".. Should I be concerned?|
|Previous:||From: Ned Lilly||Date: 2000-07-03 15:09:21|
|Subject: proposed improvements to PostgreSQL license|
pgsql-committers by date
|Next:||From: Bruce Momjian - CVS||Date: 2000-07-03 16:01:29|
|Subject: pgsql/doc/src/sgml (func.sgml)|
|Previous:||From: eisentrp||Date: 2000-07-03 12:37:14|
|Subject: Re: pgsql/src/backend/postmaster (postmaster.c) |