On 27/07/16 18:54, Chris Travers wrote: > Another one I think they obliquely referred to (in the subtle problems > section) was the fact that if you have longer-running queries on the > replica with a lot of updates, you can get funny auto-vacuum-induced > errors (writes from autovacuum on the master can interrupt queries on > the slave). BTW if there is interest in what could be done for that, > something which allows autovacuum to decide how long to wait before > cleaning up dead tuples would be a great enhancement. You mean something like hot_standby_feedback? https://www.postgresql.org/docs/current/static/runtime-config-replication.html#GUC-HOT-STANDBY-FEEDBACK -- Vik Fearing +33 6 46 75 15 36 http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
