From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sergei Kornilov <sk@zsrv.org>
Cc: alexey.ermakov@dataegret.com <alexey.ermakov@dataegret.com>
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: Sun, 22 Sep 2019 15:06:07 -0400
Message-ID: <21601.1569179167@sss.pgh.pa.us> (raw)
In-Reply-To: <158201568991600@myt5-2a1eccb4c218.qloud-c.yandex.net>
References: <16016-ed0345229ddc484c@postgresql.org>
<158201568991600@myt5-2a1eccb4c218.qloud-c.yandex.net>
Sergei Kornilov <sk@zsrv.org> writes:
> Seems I have testcase for this report:
If you have a test case, could you collect stack traces from each
of the stuck processes? That would eliminate a lot of hypothesizing.
regards, tom lane
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: tgl@sss.pgh.pa.us, sk@zsrv.org, alexey.ermakov@dataegret.com
Subject: Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
In-Reply-To: <21601.1569179167@sss.pgh.pa.us>
References: <16016-ed0345229ddc484c@postgresql.org> <158201568991600@myt5-2a1eccb4c218.qloud-c.yandex.net> <21601.1569179167@sss.pgh.pa.us>
* 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