aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/funcs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-08-24 02:18:32 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-08-24 02:18:32 +0000
commit7fc7a7c4d082bfbd579f49e92b046dd51f1faf5f (patch)
treee19eb3522dff2a147be330e6388980e4ff2be803 /src/tutorial/funcs.c
parentcab9a0656c36739f59277b34fea8ab9438395869 (diff)
downloadpostgresql-7fc7a7c4d082bfbd579f49e92b046dd51f1faf5f.tar.gz
postgresql-7fc7a7c4d082bfbd579f49e92b046dd51f1faf5f.zip
Fix a violation of WAL coding rules in the recent patch to include an
"all tuples visible" flag in heap page headers. The flag update *must* be applied before calling XLogInsert, but heap_update and the tuple moving routines in VACUUM FULL were ignoring this rule. A crash and replay could therefore leave the flag incorrectly set, causing rows to appear visible in seqscans when they should not be. This might explain recent reports of data corruption from Jeff Ross and others. In passing, do a bit of editorialization on comments in visibilitymap.c.
Diffstat (limited to 'src/tutorial/funcs.c')
0 files changed, 0 insertions, 0 deletions