Skip site navigation (1) Skip section navigation (2)

Re: We probably need autovacuum_max_wraparound_workers

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PgHacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: We probably need autovacuum_max_wraparound_workers
Date: 2012-06-29 02:15:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
* Josh Berkus (josh(at)agliodbs(dot)com) wrote:
> I don't find Stephen's proposal of goal-based solutions to be practical.
>  A goal-based approach makes the assumption that database activity is
> predictable, and IME most databases are anything but.

We're talking about over the entire transaction space, and we can be
pretty liberal, in my view, with our estimates.  If we get it right, we
might risk doing more autovac's for wraparound than strictly necessary,
but they should happen over a sufficient time that it doesn't cause
performance issues.

One definite problem with this, of course, is that the wraparound
autovac can't be stopped and restarted, and anything that increases the
amount of wall-clock time required to complete the autovac will
necessairly increase the risk that we'll lose a bunch of work due to a
database restart.



In response to

pgsql-hackers by date

Next:From: Etsuro FujitaDate: 2012-06-29 02:22:15
Subject: Re: [PATCH] Lazy hashaggregate when no aggregation is needed
Previous:From: Josh BerkusDate: 2012-06-29 01:57:24
Subject: Re: We probably need autovacuum_max_wraparound_workers

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group