From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Kevin Grittner <kevin.grittner@wicourts.gov>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Cc: Ireneusz Pluta <ipluta@wp.pl>
Subject: Re: Autovacuum and invalid page header
Date: Fri, 14 May 2010 00:50:39 -0400
Message-ID: <14800.1273812639@sss.pgh.pa.us> (raw)
In-Reply-To: <1273811839-sup-7071@alvh.no-ip.org>
References: <4BEA8CD0.8070108@wp.pl>
<4BEBC57002000025000316A3@gw.wicourts.gov>
<1273811839-sup-7071@alvh.no-ip.org>
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Yeah, maybe we should make it put the failed table at the end of the
> list, for the next run. This is not simple to implement, if only
> because autovac workers don't have any way to persist state from one run
> to the next. But this kind of thing causes enough problems that it's
> probably worth it.
> One thing to keep in mind, though, is that a persistent error in a
> single table is enough to keep a database's datfrozenxid from advancing,
> and thus shut down in case the wraparound horizon comes too close. So
> perhaps what we need is more visibility into autovacuum problems.
+1 for the latter. A recurrent vacuum failure is something that needs
to be dealt with ASAP, not partially-worked-around.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, kevin.grittner@wicourts.gov, ipluta@wp.pl
Subject: Re: Autovacuum and invalid page header
In-Reply-To: <14800.1273812639@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox