Heikki Linnakangas <heikki@enterprisedb.com> writes:
> This bug seems to be introduced by this recent change to avoid memory
> leakage:
I see no crash in CVS tip --- I believe it's same bug fixed here:
2006-12-07 19:40 tgl
* src/backend/executor/: spi.c (REL8_2_STABLE), spi.c: Avoid double
free of _SPI_current->tuptable. AtEOSubXact_SPI() now tries to
release it in a subtransaction abort, but this neglects possibility
that someone outside SPI already did. Fix is for spi.c to forget
about a tuptable as soon as it's handed it back to the caller. Per
bug #2817 from Michael Andreen.
regards, tom lane