aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2013-02-01 12:00:40 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2013-02-01 12:10:10 -0300
commit231dbb3c9be755eebdf677b469f2dd4494e7937f (patch)
treea50fbbbd67a6c64563b18883a510fc1cd68e09f8
parent1a7cd9f78a60110116afa9dd3951c7ec84cf0ac9 (diff)
downloadpostgresql-231dbb3c9be755eebdf677b469f2dd4494e7937f.tar.gz
postgresql-231dbb3c9be755eebdf677b469f2dd4494e7937f.zip
Fix typo in freeze_table_age implementation
The original code used freeze_min_age instead of freeze_table_age. The main consequence of this mistake is that lowering freeze_min_age would cause full-table scans to occur much more frequently, which causes serious issues because the number of writes required is much larger. That feature (freeze_min_age) is supposed to affect only how soon tuples are frozen; some pages should still be skipped due to the visibility map. Backpatch to 8.4, where the freeze_table_age feature was introduced. Report and patch from Andres Freund
-rw-r--r--src/backend/commands/vacuum.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/commands/vacuum.c b/src/backend/commands/vacuum.c
index 9b5b79fdcc5..656b90eed36 100644
--- a/src/backend/commands/vacuum.c
+++ b/src/backend/commands/vacuum.c
@@ -446,7 +446,7 @@ vacuum_set_xid_limits(int freeze_min_age,
* VACUUM schedule, the nightly VACUUM gets a chance to freeze tuples
* before anti-wraparound autovacuum is launched.
*/
- freezetable = freeze_min_age;
+ freezetable = freeze_table_age;
if (freezetable < 0)
freezetable = vacuum_freeze_table_age;
freezetable = Min(freezetable, autovacuum_freeze_max_age * 0.95);