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: Sat, 19 Nov 2022 12:02:32 -0500
Message-ID: <2605699.1668877352@sss.pgh.pa.us> (raw)
In-Reply-To: <475e579b-6910-91e6-65bd-513fcf3db1da@darold.net>
References: <45c93d57-9973-248e-d2df-e02ca9af48d4@darold.net>
<1847848.1668704358@sss.pgh.pa.us>
<475e579b-6910-91e6-65bd-513fcf3db1da@darold.net>
Gilles Darold <gilles@darold.net> writes:
> Le 17/11/2022 à 17:59, Tom Lane a écrit :
>> 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.
> Here are the different patched following the PostgreSQL version from 11
> to 14, they should apply on the corresponding stable branches.
Reviewed and pushed --- thanks for doing the legwork!
Trawling the commit log, I found the follow-on patch 3e6e86abc,
which fixed another issue of the same kind. I back-patched that
too.
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: <2605699.1668877352@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