Message-ID: <7a4f88eeb049543c0508a343ba4bf274dc10b487.camel@cybertec.at>
Subject: Re: canceling statement coming in slave instance
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Rohit Arora <arora.leo9@gmail.com>, shreeyansh2014@gmail.com
Cc: pgsql-admin@postgresql.org
Date: Tue, 27 Nov 2018 06:12:24 +0100
In-Reply-To: 
 <CAMUAjH805S-35_QetGAHn2SOZe_=YAdcLN_CeXfzYt2KBMxnTw@mail.gmail.com>
References: 
	<CAMUAjH9FaYYJFkY6K5Exnb4ZA8KiPxOCqFCL9-AMTi+24ZYxdA@mail.gmail.com>
	 <CAMUAjH_btdjCoTvOW-rkc0KpkVx3TAv1P9C8AXjGro07T8n4wQ@mail.gmail.com>
	 <CAGDYbUO7wMjsrf3Cu1vtnzXK3=LcYp=1fQEbwKBN8k2J2nowiQ@mail.gmail.com>
	 <CAGDYbUNT5++yxrzv_wPtAYPF_RYmUpY+cLSV8nkU8cN0tFaRtA@mail.gmail.com>
	 <CAMUAjH805S-35_QetGAHn2SOZe_=YAdcLN_CeXfzYt2KBMxnTw@mail.gmail.com>
Organization: Cybertec
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

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