From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Invent a memory context reset/delete callback mechanism. |
Date: | 2015-02-27 23:44:55 |
Message-ID: | CA+U5nMJ3dS4WS5DE7vjG+=zywQLbXP4N2_-8So8_FTeea5iu8A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 27 February 2015 at 22:17, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Invent a memory context reset/delete callback mechanism.
>
> This allows cleanup actions to be registered to be called just before a
> particular memory context's contents are flushed (either by deletion or
> MemoryContextReset). The patch in itself has no use-cases for this, but
> several likely reasons for wanting this exist.
>
> 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.
Please can you document this in src/backend/utils/mmgr/README or other place?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, RemoteDBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2015-02-28 01:26:59 | Re: [COMMITTERS] pgsql: Invent a memory context reset/delete callback mechanism. |
Previous Message | Tom Lane | 2015-02-27 23:19:27 | pgsql: Suppress uninitialized-variable warning from less-bright compile |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-02-28 00:37:49 | Re: Providing catalog view to pg_hba.conf file - Patch submission |
Previous Message | David G Johnston | 2015-02-27 23:27:43 | Re: logical column ordering |