From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
Cc: | Dave Page <dpage(at)postgresql(dot)org>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: 8.2 pl/pgsql crash bug (WAS: [pgadmin-support] Error craches |
Date: | 2006-12-12 15:34:41 |
Message-ID: | 3136.1165937681@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Heikki Linnakangas <heikki(at)enterprisedb(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-12-12 16:48:22 | Re: SPI_getvalue calls output function w/o pushing existing SPI connection + 2 extra issues |
Previous Message | pgsql-bugs | 2006-12-12 14:16:08 | BUG #2824: Problem with installation by Remote Desktop |