| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Karl Hafner *EXTERN*" <karl(at)scoreloop(dot)com>, Strahinja Kustudic <strahinjak(at)nordeus(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: MultiXactId Error in Autovacuum |
| Date: | 2013-11-19 10:00:18 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17C5C88A@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Karl Hafner wrote:
> Since the autovacuum process is failing each time because of: "ERROR: MultiXactId 2683601542 does no
> longer exist -- apparent wraparound", I have expected the manual vacuum also to fail because of the
> same error.
> I've tried it anyway. Well ... manual vacuum also fails unfortunately.
Do you know if you experienced transaction ID wraparound as the
message suggests?
Are there any other questionable messages in the log?
What do you get for the following queries:
SELECT txid_current();
SELECT datname, datfrozenxid FROM pg_database;
SELECT current_setting('autovacuum_freeze_max_age'),
current_setting('vacuum_freeze_min_age'),
current_setting('vacuum_freeze_table_age');
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gary Stainburn | 2013-11-19 11:08:18 | Postgresql not accessible, recovering |
| Previous Message | Karl Hafner | 2013-11-18 15:30:41 | Re: MultiXactId Error in Autovacuum |