| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dinesh Bhandary <dbhandary(at)switchfly(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:17:30 |
| Message-ID: | 20140829191729.GI7705@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Dinesh Bhandary wrote:
> 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.
No, leave the offset alone. I meant that the "x" value (i.e. the part
before the comma) should stay unchanged; you only need to change the
"oldest" value, which is "y" (part after the comma).
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dinesh Bhandary | 2014-08-29 20:02:45 | Re: BUG #11264: Auto vacuum wraparound job blocking everything |
| Previous Message | Dinesh Bhandary | 2014-08-29 19:09:40 | Re: BUG #11264: Auto vacuum wraparound job blocking everything |