Re: canceling statement coming in slave instance

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Rohit Arora <arora(dot)leo9(at)gmail(dot)com>, shreeyansh2014(at)gmail(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: canceling statement coming in slave instance
Date: 2018-11-27 05:12:24
Message-ID: 7a4f88eeb049543c0508a343ba4bf274dc10b487.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, 2018-11-27 at 10:20 +0530, Rohit Arora wrote:
[is fighting canceled queries dur to replication conflicts, but fears primary bloat]
In that case, I would set

max_standby_streaming_delay = -1
max_standby_archive_delay = -1
hot_standby_feedback = off

Then no queries should get canceled on the standby, and long queries
on the standby won't cause bloat on the primary.

The price you are paying is delayed replication.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Moin Akther 2018-11-28 14:22:22 Manual Vacuum Analyze Take More Time
Previous Message Rohit Arora 2018-11-27 04:50:13 Re: canceling statement coming in slave instance