| 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-03-01 16:27:33 |
| Message-ID: | CA+U5nM+=pamKBwo7Z-pdH2iRiHsY=18QOgWO1NV+roJt_0nEAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 28 February 2015 at 01:34, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> 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.
>
>> Please can you document this in src/backend/utils/mmgr/README or other place?
>
> Is anybody still reading that? OK, done.
There was a recent question about memory management, so people do ask
and that's still where we send 'em.
Thanks.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, RemoteDBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-03-01 17:31:39 | pgsql: Move memory context callback declarations into palloc.h. |
| Previous Message | Alvaro Herrera | 2015-03-01 14:58:46 | pgsql: Fix intermittent failure in event_trigger test |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2015-03-01 17:20:55 | Re: Odd behavior of updatable security barrier views on foreign tables |
| Previous Message | Andrew Dunstan | 2015-03-01 15:49:58 | Re: mogrify and indent features for jsonb |