I have a follow up question on hot_standby_feedback.
If I have 3 read replicas that all have this set to ON, and someone runs a very long query on one of the replicas, can all three replicas fall behind until the query is finished? This is the behavior I observed more than once, but I can’t seem to be able to explain it based on the documented behavior of this parameter.
A related question is — how can you avoid doing auto vacuum during the busy peak hours, and do more aggressive auto vacuuming at night during low traffic? Is that possible?
I tried achieving that with a manual vacuum, but that causes all replicas to get far behind while it’s running, which is also not acceptable.
Thanks so much!
On Thu, Oct 31, 2019 at 1:02 AM Andreas Kretschmer <andreas@xxxxxxxxxxxxxxx> wrote:
Am 31.10.19 um 06:21 schrieb M Tarkeshwar Rao:
>
> Can you please suggest how to configure hot_standby_feedback?
>
>
turn it on if you want execute long running queries on the standby, keep
in mind it can lead to more bloat on the master.
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com
Konstantin Gredeskoul
CEO & Principal Consultant ● ReinventONE Inc ● https://reinvent.one/ ● (415) 265-1054
CEO & Principal Consultant ● ReinventONE Inc ● https://reinvent.one/ ● (415) 265-1054
