From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
---|---|
To: | vik(at)2ndquadrant(dot)fr |
Cc: | chris(dot)travers(at)gmail(dot)com, scottm(at)openscg(dot)com, achill(at)matrix(dot)gatewaynet(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Uber migrated from Postgres to MySQL |
Date: | 2016-08-05 08:16:36 |
Message-ID: | 20160805.171636.594438385083829740.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> 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
I wonder if their problem could be fixed by using
hot_standby_feedback. I have encountered similar problem but it seems
hot_standby_feedback was not any help in this case:
https://www.postgresql.org/message-id/20130829.164457.863984798767991096.t-ishii%40sraoss.co.jp
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2016-08-05 10:27:00 | Re: Uber migrated from Postgres to MySQL |
Previous Message | John R Pierce | 2016-08-05 00:44:07 | Re: Tunning Server 9.1. |