| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 16:47:26 |
| Message-ID: | Pine.LNX.4.21.0007031845340.355-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Tom Lane writes:
> OK, do you want to fix it, or shall I?
I will. I got some half-finished code lying around that touches that.
> 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.
Well, I would really like a way to register an entire memory context to be
swept away by elog(ERROR). But that's probably too specialized. But yes, I
will look into that.
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-07-03 19:20:31 | Memory-context slinging |
| Previous Message | Peter Eisentraut - PostgreSQL | 2000-07-03 16:35:39 | pgsql/src/bin/pg_dump (pg_dumpall.sh Makefile pg_dumpall) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-07-03 19:20:31 | Memory-context slinging |
| Previous Message | Michael J Schout | 2000-07-03 16:02:28 | Strange "NOTICE".. Should I be concerned? |