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

Hi Alvaro,

I was killing to reproduce the bug.Once it is fixed we have no need to
kill these jobs.
Now we still have this production server not running in auto vacuum till
we apply the fix during next maintenance window. Is running vacuum
manually safe, or we may run into the same issue as auto vacuum tx
wraparound job? I am thinking max_freeze set to 500 million, manual
vacuum won¹t freeze xids, and it may be ok to run. But I am not completely
sure and worried about the same issue happening in production even with
manual vacuum. Please let me know.

Thanks a lot for your help. Much appreciated.
Dinesh

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

>Dinesh Bhandary wrote:
>> I think the fix is working. Now I am able to kill copy job while auto
>> vacuum job is going on that table.
>
>I hope this killing of autovacuum jobs is not continued operational
>practice. You need whole-table vacuums of all your tables once in a
>while. (Note you can increase the "freeze_table_age" parameters if you
>want to be forced to do that less frequently. See the docs.)
>
>> Since I am setting pg_resetxlog on the primary, do I need to do that on
>> the slave too? Please let me know
>
>No, the slave should fix itself once the checkpoint record is replayed.
>
>--
>Álvaro Herrera http://www.2ndQuadrant.com/
>PostgreSQL Development, 24x7 Support, Training & Services