| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: autovacuum not prioritising for-wraparound tables |
| Date: | 2013-01-28 13:11:12 |
| Message-ID: | 510678F0.2070909@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> So I think we need to sort by age(relfrozenxid) in tables that are over
> the anti-wraparound limit. Given your code that doesn't seem to be that
> hard?
I might also suggest that we think about changing the defaults for
wraparound vacuum behavior. Partcularly, the fact that
vacuum_freeze_min_age is 50% of autovacuum_freeze_max_age by default is
optimal for absolutely nobody, and forces re-wraparound vacuuming of
wraparound tables which were just recently wraparound-vacuumed. We
should lower vacuum_freeze_min_age to something sane, like 1000000.
(background:
http://www.databasesoup.com/2012/10/freezing-your-tuples-off-part-2.html)
Also, while I don't know if Alvaro's optimization is a net gain or not
(It might be), I do agree that backpatching it is not worth considering.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2013-01-28 13:39:22 | Re: Performance Improvement by reducing WAL for Update Operation |
| Previous Message | Fabrízio de Royes Mello | 2013-01-28 13:02:58 | Re: pg_catalog |