Move the tuple freezing point in CLUSTER to a point further back in the past,
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Thu, 17 May 2007 15:28:29 +0000 (15:28 +0000)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Thu, 17 May 2007 15:28:29 +0000 (15:28 +0000)
commit12e6497a5a3cea7f0fd48d39697758f9e9839189
treebd68a373e4a0381eef76dbf0d77965f0a1288334
parent09514dda9be0c2d301378aa075699d110ce7ed2a
Move the tuple freezing point in CLUSTER to a point further back in the past,
to avoid losing useful Xid information in not-so-old tuples.  This makes
CLUSTER behave the same as VACUUM as far a tuple-freezing behavior goes
(though CLUSTER does not yet advance the table's relfrozenxid).

While at it, move the actual freezing operation in rewriteheap.c to a more
appropriate place, and document it thoroughly.  This part of the patch from
Tom Lane.
src/backend/access/heap/rewriteheap.c
src/backend/commands/cluster.c
src/backend/commands/vacuum.c
src/backend/commands/vacuumlazy.c
src/include/access/rewriteheap.h
src/include/commands/vacuum.h