Skip site navigation (1) Skip section navigation (2)

pgsql: Avoid double free of _SPI_current->tuptable.

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid double free of _SPI_current->tuptable.
Date: 2006-12-08 00:40:27
Message-ID: 20061208004027.C37F99F9C9E@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
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.

Modified Files:
--------------
    pgsql/src/backend/executor:
        spi.c (r1.165 -> r1.166)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/spi.c.diff?r1=1.165&r2=1.166)

pgsql-committers by date

Next:From: Tom LaneDate: 2006-12-08 00:40:33
Subject: pgsql: Avoid double free of _SPI_current->tuptable.
Previous:From: Tom LaneDate: 2006-12-07 19:33:48
Subject: pgsql: Repair incorrect placement of WHERE clauses when there are

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group