From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: domain_in performance considerations |
Date: | 2006-04-06 14:12:57 |
Message-ID: | 17798.1144332777@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> This is a shot in the dark, but I remember you commenting awhile back
> that there was a way to register a callback to be called on memory
> context reset or delete.
AFAIR there's no such thing associated with memory contexts per se.
There is one for EStates, but that requires access to an outer EState,
which is exactly what we lack for the other solution too.
I wonder though if we shouldn't invent one for memory contexts. Maybe
even replace the EState-specific shutdown callback with mcontext cleanup
on its query context?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Caduto | 2006-04-06 14:13:47 | Re: Windows installer bugs (was: [BUGS] BUG #2374: Installation |
Previous Message | Alvaro Herrera | 2006-04-06 13:55:39 | Re: domain_in performance considerations |