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

Re: pgsql/src/backend/postmaster (postmaster.c)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql/src/backend/postmaster (postmaster.c)
Date: 2000-07-03 15:16:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackers
eisentrp(at)csis(dot)gvsu(dot)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

In response to


pgsql-hackers by date

Next:From: Michael J SchoutDate: 2000-07-03 16:02:28
Subject: Strange "NOTICE".. Should I be concerned?
Previous:From: Ned LillyDate: 2000-07-03 15:09:21
Subject: proposed improvements to PostgreSQL license

pgsql-committers by date

Next:From: Bruce Momjian - CVSDate: 2000-07-03 16:01:29
Subject: pgsql/doc/src/sgml (func.sgml)
Previous:From: eisentrpDate: 2000-07-03 12:37:14
Subject: Re: pgsql/src/backend/postmaster (postmaster.c)

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