| From: | Dinesh Bhandary <dbhandary(at)switchfly(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #11264: Auto vacuum wraparound job blocking everything |
| Date: | 2014-08-29 19:09:40 |
| Message-ID: | 9ac49eee319c43f6a344a2d5d2c38093@CO2PR05MB569.namprd05.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
and that should fix it. The oldestMulti value in pg_control would get updated by itself some time later. If you experience stalls before oldestMulti fixes itself, you could stop the server (cleanly!) and then pg_resetxlog -m x,y where x is the correct nextMulti value from pg_controldata and y is 20783.
Are you referreing to NextMultiXactId of current pg_controldata ( from postgres 9.3.5) for x?
There is also NextMultiOffset, not sure If you meant to reset this. Please confirm.
Thanks,
Dinesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-08-29 19:17:30 | Re: BUG #11264: Auto vacuum wraparound job blocking everything |
| Previous Message | David G Johnston | 2014-08-29 15:16:10 | Re: BUG #11304: UNION query with NULL values fails |