From: Alexey Ermakov <alexey.ermakov@dataegret.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sergei Kornilov <sk@zsrv.org>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
Date: Sat, 02 Nov 2019 23:30:45 +0600
Message-ID: <5DBDBD45.1020406@dataegret.com> (raw)
In-Reply-To: <30149.1572707406@sss.pgh.pa.us>
References: <16016-ed0345229ddc484c@postgresql.org>
<158201568991600@myt5-2a1eccb4c218.qloud-c.yandex.net>
<21601.1569179167@sss.pgh.pa.us>
<5DBBF7B5.6040002@dataegret.com>
<30149.1572707406@sss.pgh.pa.us>
On 11/2/19 21:10, Tom Lane wrote:
> This does not look like a deadlock: the startup process is just biding
> its time until the standby delay timeout elapses, after which it's
> gonna kill the conflicting queries.
>
> It is, perhaps, arguable that it's a damn bad idea to allow
> max_standby_streaming_delay or max_standby_archive_delay to be
> set to "forever".
>
>
I agree, allowing max_standby_streaming_delay be set to -1 is perhaps
not a good idea. there is although case when such setting could be used
now, see "BUG #14044: Queries immediately conflict with recovery when
recovery_min_apply_delay is used". [1]
[1] https://postgr.es/m/20160324204550.2920.87946%40wrigleys.postgresql.org
--
Alexey Ermakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: alexey.ermakov@dataegret.com, tgl@sss.pgh.pa.us, sk@zsrv.org
Subject: Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
In-Reply-To: <5DBDBD45.1020406@dataegret.com>
References: <16016-ed0345229ddc484c@postgresql.org> <158201568991600@myt5-2a1eccb4c218.qloud-c.yandex.net> <21601.1569179167@sss.pgh.pa.us> <5DBBF7B5.6040002@dataegret.com> <30149.1572707406@sss.pgh.pa.us> <5DBDBD45.1020406@dataegret.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox