From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gilles Darold <gilles@darold.net>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [BUG] pg_dump blocked
Date: Thu, 17 Nov 2022 11:59:18 -0500
Message-ID: <1847848.1668704358@sss.pgh.pa.us> (raw)
In-Reply-To: <45c93d57-9973-248e-d2df-e02ca9af48d4@darold.net>
References: <45c93d57-9973-248e-d2df-e02ca9af48d4@darold.net>
Gilles Darold <gilles@darold.net> writes:
> I have an incorrect behavior with pg_dump prior PG version 15. With
> PostgreSQL 15, thanks to commit e3fcbbd623b9ccc16cdbda374654d91a4727d173
> the problem is gone but for older versions it persists with locks on
> partitioned tables.
I didn't want to back-patch e3fcbbd62 at the time, but it's probably aged
long enough now to be safe to back-patch. If we do anything here,
it should be to back-patch the whole thing, else we've only partially
fixed the issue.
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, gilles@darold.net
Subject: Re: [BUG] pg_dump blocked
In-Reply-To: <1847848.1668704358@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