| 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 21:07:53 |
| Message-ID: | 20140829210753.GK7705@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dinesh Bhandary | 2014-08-29 21:13:41 | Re: BUG #11264: Auto vacuum wraparound job blocking everything |
| Previous Message | Dinesh Bhandary | 2014-08-29 20:02:45 | Re: BUG #11264: Auto vacuum wraparound job blocking everything |