| From: | alvherre(at)postgresql(dot)org (Alvaro Herrera) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Have the rewriteheap code freeze old tuples. |
| Date: | 2007-05-16 16:36:56 |
| Message-ID: | 20070516163656.B456E9FBAAB@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Have the rewriteheap code freeze old tuples. This is safe because it is only
applied to live tuples older than a recent Xmin, not to tuples that may be part
of an update chain. Those still keep their original markings.
This patch makes it possible for CLUSTER to advance relfrozenxid, thus avoiding
the need of vacuuming the table for Xid wraparound purposes. That will be
patched separately.
Patch from Heikki Linnakangas.
Modified Files:
--------------
pgsql/src/backend/access/heap:
rewriteheap.c (r1.3 -> r1.4)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/rewriteheap.c.diff?r1=1.3&r2=1.4)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-05-16 17:28:20 | pgsql: Have TRUNCATE advance the affected table's relfrozenxid to |
| Previous Message | User H-saito | 2007-05-16 00:58:48 | odbclink - odbclink: The sample was added. |