Tom Lane wrote:
Hi,
It would be just a small change to make the code cache the EState across
calls, saving a link to it in the FmgrInfo, but I am worried about that.
If the EState's query context is made to be a child of the memory
context containing the caller's FmgrInfo, then there is no
Alvaro Herrera [EMAIL PROTECTED] 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
Neil Conway wrote some pretty nice things here:
http://www.advogato.org/person/nconway/diary.html?start=26
but commented
It would be worthwhile to investigate whether this results in a
performance regression, though: there's no easy way to cache the
executor machinery needed to evaluate a CHECK
