Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit217dc52

Browse files
committed
Fix oversight in EvalPlanQualFetch: after failing to lock a tuple because
someone else has just updated it, we have to set priorXmax to that tuple'sxmax (ie, the XID of the other xact that updated it) before looping back toexamine the next tuple. Obviously, the next tuple in the update chain shouldhave that XID as its xmin, not the same xmin as the preceding tuple that wehad been trying to lock. The mismatch would cause the EvalPlanQual logic todecide that the tuple chain ended in a deletion, when actually there was alive tuple that should have been found.I inserted this error when recently adding logic to EvalPlanQual to make itlock tuples before returning them (as opposed to the old method in which thelock would occur much later, causing a great deal of work to be wasted if weonly then discover someone else updated it). Sigh. Per today's report fromTakahiro Itagaki of inconsistent results during pgbench runs.
1 parent83a5a33 commit217dc52

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

‎src/backend/executor/execMain.c

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@
2626
*
2727
*
2828
* IDENTIFICATION
29-
* $PostgreSQL: pgsql/src/backend/executor/execMain.c,v 1.340 2010/01/06 03:04:01 momjian Exp $
29+
* $PostgreSQL: pgsql/src/backend/executor/execMain.c,v 1.341 2010/01/08 02:44:00 tgl Exp $
3030
*
3131
*-------------------------------------------------------------------------
3232
*/
@@ -1546,6 +1546,8 @@ EvalPlanQualFetch(EState *estate, Relation relation, int lockmode,
15461546
{
15471547
/* it was updated, so look at the updated version */
15481548
tuple.t_self=update_ctid;
1549+
/* updated row should have xmin matching this xmax */
1550+
priorXmax=update_xmax;
15491551
continue;
15501552
}
15511553
/* tuple was deleted, so give up */

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp