aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2006-01-12 21:48:53 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2006-01-12 21:48:53 +0000
commit25b9b1b0425910a8503979ddcd974a0a32998791 (patch)
treefa36e04bf52b190be04d276556c5d7e5e1743bea /src/backend/access/gist
parentdb0558c11347ad27a032e6efed509a6e99b52e67 (diff)
downloadpostgresql-25b9b1b0425910a8503979ddcd974a0a32998791.tar.gz
postgresql-25b9b1b0425910a8503979ddcd974a0a32998791.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/backend/access/gist')
0 files changed, 0 insertions, 0 deletions