From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Armand du Plessis *EXTERN*" <adp(at)bank(dot)io>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: relfrozenxid not getting reset even after manual VACUUM |
Date: | 2013-08-06 07:04:20 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17BF37DB@ntex2010a.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Armand du Plessis wrote:
> We're running into a scenario where despite doing a manual vacuum as a superuser the relfrozenxid for
> one relation now dangerously close to wraparound is not getting reset.
>
> It's a Postgres 9.2.3 cluster. We shutdown other access to the machine while running the VACUUM to
> ensure it could complete quick enough with an aggressive vacuum (vacuum_cost_limit 10000 and no
> delay). The previous autovacuum was running for days without completing.
>
> There's also no old transactions in either pg_prepared_xacts or pg_stat_activity.
> The tail-end of the vacuum log:
[...]
> DETAIL: 701995 dead row versions cannot be removed yet.
That's your problem. Somebody must have been using these rows, unless
there is a bug. That's an awfully high number too.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2013-08-06 07:10:16 | Re: After upgrading from 9.1.1 to 9.1.9, pgadmin's server status window gives error |
Previous Message | Sergey Konoplev | 2013-08-06 02:25:40 | Re: Simple question on fail over and config files |