pgsql: Fix oversight in new EvalPlanQual logic: the second loop over the

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix oversight in new EvalPlanQual logic: the second loop over the
Date: 2010-07-28 17:21:56
Message-ID: 20100728172156.60E697541D5@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix oversight in new EvalPlanQual logic: the second loop over the ExecRowMark
list in ExecLockRows() forgot to allow for the possibility that some of the
rowmarks are for child tables that aren't relevant to the current row.
Per report from Kenichiro Tanaka.

Modified Files:
--------------
pgsql/src/backend/executor:
nodeLockRows.c (r1.5 -> r1.6)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeLockRows.c?r1=1.5&r2=1.6)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-07-28 17:22:03 pgsql: Fix oversight in new EvalPlanQual logic: the second loop over the
Previous Message Simon Riggs 2010-07-28 05:22:24 pgsql: Reduce lock levels of CREATE TRIGGER and some ALTER TABLE, CREATE