| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Replace hardcoded 200000000 with autovacuum_freeze_max_age |
| Date: | 2013-11-30 01:06:09 |
| Message-ID: | [email protected] |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Replace hardcoded 200000000 with autovacuum_freeze_max_age
Parts of the code used autovacuum_freeze_max_age to determine whether
anti-multixact-wraparound vacuums are necessary, while others used a
hardcoded 200000000 value. This leads to problems when
autovacuum_freeze_max_age is set to a non-default value. Use the latter
everywhere.
Backpatch to 9.3, where vacuuming of multixacts was introduced.
Andres Freund
Branch
------
REL9_3_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/d9484ab5f3cbcfea64536fec333723f9aa4c0b2c
Modified Files
--------------
src/backend/access/transam/multixact.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-11-30 01:06:10 | pgsql: Truncate pg_multixact/'s contents during crash recovery |
| Previous Message | Alvaro Herrera | 2013-11-30 01:06:08 | pgsql: Replace hardcoded 200000000 with autovacuum_freeze_max_age |