Thread: pgsql: Repair "Halloween problem" in EvalPlanQual: a tuple that's been

pgsql: Repair "Halloween problem" in EvalPlanQual: a tuple that's been

From

tgl@postgresql.org (Tom Lane)

Date:

12 January 2006, 20:49:38

Log Message:
-----------
Repair "Halloween problem" in EvalPlanQual: a tuple that's been inserted by
our own command (or more generally, xmin = our xact and cmin >= current
command ID) should not be seen as good.  Else we may try to update rows
we already updated.  This error was inserted last August while fixing the
even bigger problem that the old coding wouldn't see *any* tuples inserted
by our own transaction as good.  Per report from Euler Taveira de Oliveira.

Tags:
----
REL7_4_STABLE

Modified Files:
--------------
    pgsql/src/backend/commands:
        trigger.c (r1.159.2.1 -> r1.159.2.2)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/trigger.c.diff?r1=1.159.2.1&r2=1.159.2.2)
    pgsql/src/backend/executor:
        execMain.c (r1.220.2.3 -> r1.220.2.4)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execMain.c.diff?r1=1.220.2.3&r2=1.220.2.4)
    pgsql/src/include/executor:
        executor.h (r1.102.2.4 -> r1.102.2.5)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/executor/executor.h.diff?r1=1.102.2.4&r2=1.102.2.5)