Re: BUG #11264: Auto vacuum wraparound job blocking everything

I think the fix is working. Now I am able to kill copy job while auto
vacuum job is going on that table.

Since I am setting pg_resetxlog on the primary, do I need to do that on
the slave too? Please let me know

Thanks.
Dinesh

On 8/29/14, 12:17 PM, "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com> wrote:

>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