From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, Ireneusz Pluta <ipluta(at)wp(dot)pl> |
Subject: | Re: Autovacuum and invalid page header |
Date: | 2010-05-14 04:50:39 |
Message-ID: | 14800.1273812639@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2010-05-14 05:29:39 | Re: List traffic |
Previous Message | Alvaro Herrera | 2010-05-14 04:40:41 | Re: Autovacuum and invalid page header |