From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: pg_upgrade errno
Date: Mon, 1 Aug 2022 09:19:10 +0900
Message-ID: <Yucb/jpcRFFTz2IR@paquier.xyz> (raw)
In-Reply-To: <1500697.1659311005@sss.pgh.pa.us>
References: <20220731134135.GY15006@telsasoft.com>
<YucSnskQnxLc4ANF@paquier.xyz>
<1500697.1659311005@sss.pgh.pa.us>
On Sun, Jul 31, 2022 at 07:43:25PM -0400, Tom Lane wrote:
> It's been wrong a lot longer than that, no?
Since the beginning of times. But we've never really cared about
fixing such errno behaviors based on their unlikeliness, have we? I
don't mind doing a backpatch here, though, that's isolated enough.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (832B, ../Yucb%2FjpcRFFTz2IR@paquier.xyz/2-signature.asc)
download
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: michael@paquier.xyz, tgl@sss.pgh.pa.us, pryzby@telsasoft.com, peter.eisentraut@enterprisedb.com
Subject: Re: pg_upgrade errno
In-Reply-To: <Yucb/jpcRFFTz2IR@paquier.xyz>
* 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