From: | piuschan <pchan(at)contigo(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: automatic vacuum on pg_statistic pg_toast area blocks all queries in hot standby |
Date: | 2014-09-23 17:47:09 |
Message-ID: | 1411494429599-5820171.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
Thanks for your feedback. Someone finally replies to this thread. I am not
quite clear of your solution, so I need more info from you.
First of all, we do not enable hot_standby_feedback on SLAVE DB.
postgres=# show hot_standby_feedback;
hot_standby_feedback
----------------------
off
(1 row)
Secondly, where do you run "select txid_current() into res1" and "select
txid_current() into res2" ?
Even if you set MASTER vacuum_defer_cleanup_age to certain value, autovacuum
still can kick in anytime and may conflict query on the target table. So
setting vacuum_defer_cleanup_age to a value can really reduce the chance of
such situation?
Thanks a lot,
Pius
--
View this message in context: http://postgresql.1045698.n5.nabble.com/automatic-vacuum-on-pg-statistic-pg-toast-area-blocks-all-queries-in-hot-standby-tp5807143p5820171.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | ddv | 2014-09-23 18:40:27 | Re: automatic vacuum on pg_statistic pg_toast area blocks all queries in hot standby |
Previous Message | ddv | 2014-09-23 17:18:38 | Re: automatic vacuum on pg_statistic pg_toast area blocks all queries in hot standby |