]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 90cbc63) | patch
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)
commit3b0347b36e1f59e5db95e8994948d850bfc90472
tree437bc425e994ac31daf0775e476b7315b939070ctree | snapshot
parent90cbc63fd10adaeb01c3180156e0e48eee08b5edcommit | diff
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 diff | blob | history
src/backend/commands/cluster.c diff | blob | history
src/backend/commands/vacuum.c diff | blob | history
src/backend/commands/vacuumlazy.c diff | blob | history
src/include/access/rewriteheap.h diff | blob | history
src/include/commands/vacuum.h diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.