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

In response to

• Re: pgsql/src/backend/postmaster (postmaster.c) at 2000-07-03 15:16:14 from Tom Lane

Responses

• Memory-context slinging at 2000-07-03 19:20:31 from Tom Lane

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2000-07-03 19:20:31
	Subject: Memory-context slinging
Previous:	From: Michael J Schout	Date: 2000-07-03 16:02:28
	Subject: Strange "NOTICE".. Should I be concerned?

pgsql-committers by date

Next:	From: Tom Lane	Date: 2000-07-03 19:20:31
	Subject: Memory-context slinging
Previous:	From: Peter Eisentraut - PostgreSQL	Date: 2000-07-03 16:35:39
	Subject: pgsql/src/bin/pg_dump (pg_dumpall.sh Makefile pg_dumpall)