mirror of
https://github.com/postgres/postgres.git
synced 2025-07-18 17:42:25 +03:00
Aggressively freeze tables when CLUSTER or VACUUM FULL rewrites them.
We haven't wanted to do this in the past on the grounds that in rare
cases the original xmin value will be needed for forensic purposes, but
commit 37484ad2aa
removes that objection,
so now we can.
Per extensive discussion, among many people, on pgsql-hackers.
This commit is contained in:
@ -345,7 +345,7 @@ rewrite_heap_tuple(RewriteState state,
|
||||
|
||||
/*
|
||||
* While we have our hands on the tuple, we may as well freeze any
|
||||
* very-old xmin or xmax, so that future VACUUM effort can be saved.
|
||||
* eligible xmin or xmax, so that future VACUUM effort can be saved.
|
||||
*/
|
||||
heap_freeze_tuple(new_tuple->t_data, state->rs_freeze_xid,
|
||||
state->rs_cutoff_multi);
|
||||
|
Reference in New Issue
Block a user