| 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: | 19451.962637374@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian - CVS | 2000-07-03 16:01:29 | pgsql/doc/src/sgml (func.sgml) |
| Previous Message | eisentrp | 2000-07-03 12:37:14 | Re: pgsql/src/backend/postmaster (postmaster.c) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael J Schout | 2000-07-03 16:02:28 | Strange "NOTICE".. Should I be concerned? |
| Previous Message | Ned Lilly | 2000-07-03 15:09:21 | proposed improvements to PostgreSQL license |