Re: Re: [COMMITTERS] pgsql: Invent a memory context reset/delete callback mechanism. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Invent a memory context reset/delete callback mechanism.
Date
Msg-id 29787.1425087767@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Invent a memory context reset/delete callback mechanism.  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Re: [COMMITTERS] pgsql: Invent a memory context reset/delete callback mechanism.  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Jeff Davis <pgsql@j-davis.com> writes:
> On Fri, 2015-02-27 at 22:17 +0000, Tom Lane wrote:
>> In passing, per discussion, rearrange some boolean fields in struct
>> MemoryContextData so as to avoid wasted padding space.  For safety,
>> this requires making allowInCritSection's existence unconditional;
>> but I think that's a better approach than what was there anyway.

> I notice that this uses the bytes in MemoryContextData that I was hoping
> to use for the memory accounting patch (for memory-bounded HashAgg).

Meh.  I thought Andres' complaint about that was unfounded anyway ;-).
But I don't really see why a memory accounting patch should be expected to
have zero footprint.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Providing catalog view to pg_hba.conf file - Patch submission
Next
From: Gavin Flower
Date:
Subject: Re: logical column ordering