Advice wanted on backend memory management - Mailing list pgsql-hackers

From Tom Lane
Subject Advice wanted on backend memory management
Date
Msg-id 309.925834075@sss.pgh.pa.us
Whole thread Raw
List pgsql-hackers
I want to change hashjoin's use of a fixed-size overflow area for tuples
that don't fit into the hashbucket they ought to go in.  Since it's
always possible for an improbably large number of tuples to hash into the
same hashbucket, the overflow area itself can overflow; without the
ability to recover from that, hashjoin is inherently unreliable.
So I think this is an important thing to fix.

To do this, I need to be able to allocate chunks of space that I will
later want to give back all at once (at the end of a hash pass).
Seems to me like a job for palloc and a special memory context ---
but I see no way in mcxt.h to create a new memory context.  How do
I do that?  Also, I'd want the new context to be a "sub-context" of
the regular execution context, in the sense that it should automatically
get released if we exit via elog(ERROR).  What are the appropriate
calls to be using for this?  If there's documentation about this stuff,
I haven't found it :-(
        regards, tom lane


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: [HACKERS] adate::Date is equiv. to adate if adate is type of Date ?
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] major flaw in 6.5beta1??? (UPDATE/INSERT waiting)