diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-02-01 12:00:40 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-02-01 12:11:33 -0300 |
| commit | 406758fd5d472e8eec93d145b860f3553dc60563 (patch) | |
| tree | ef25b06e8d4f6d01ad76f0edd17abb3b777d5ac5 | |
| parent | d1bdb35a989f1b45962c7a83372e00a71c8e6b49 (diff) | |
| download | postgresql-406758fd5d472e8eec93d145b860f3553dc60563.tar.gz postgresql-406758fd5d472e8eec93d145b860f3553dc60563.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.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/commands/vacuum.c b/src/backend/commands/vacuum.c index 2569f28b80c..dbf10401b66 100644 --- a/src/backend/commands/vacuum.c +++ b/src/backend/commands/vacuum.c @@ -665,7 +665,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); |