]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0affc29) | patch
Fix tuple-chain-moving tests to handle marked-for-update tuples correctly
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 13 Aug 2002 20:14:24 +0000 (20:14 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 13 Aug 2002 20:14:24 +0000 (20:14 +0000)
commitf8b4a2e0f0a0dd7d1cefd53d8048bfb58f33bd37
tree4cd5e3dffddec8f2c1fec1062383b4feb0ccd6cetree
parent0affc29e1e8686a0d44165f11cd7818891bcfb46commit | diff
Fix tuple-chain-moving tests to handle marked-for-update tuples correctly
(they are not part of a chain).  When failing to find a parent tuple in
an update chain, emit a warning and abandon repair_frag, but do not give
an error as before.  This should eliminate the infamous 'No one parent tuple
was found' failure, which we now realize is not a can't-happen condition
but a perfectly valid database state.  Per recent pghackers discussion.
src/backend/commands/vacuum.c diff | blob | blame | history
Mirror of https://git.postgresql.org/git/postgresql.git