aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/basics.source
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2006-01-12 21:49:19 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2006-01-12 21:49:19 +0000
commite26b09618b98358d951eb37e48df2ab6f8cb5489 (patch)
tree1590c06dce692cb37a6e4b6bb7c125156427dab2 /src/tutorial/basics.source
parent01e2a15adac9e437ac16fd0a6aef427f4eb78aad (diff)
downloadpostgresql-e26b09618b98358d951eb37e48df2ab6f8cb5489.tar.gz
postgresql-e26b09618b98358d951eb37e48df2ab6f8cb5489.zip
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.
Diffstat (limited to 'src/tutorial/basics.source')
0 files changed, 0 insertions, 0 deletions