From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Hans Buschmann <buschmann@nidsa.net>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode
Date: Tue, 17 Aug 2021 09:39:30 -0400
Message-ID: <1075837.1629207570@sss.pgh.pa.us> (raw)
In-Reply-To: <YRsYT3Fb82IYr5+F@paquier.xyz>
References: <1629039545467.80333@nidsa.net>
<YRsYT3Fb82IYr5+F@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> In short, I am planning to address this regression with the attached,
> for a combined revert of 0d70d30, 5c33ba5 and 92436a7.
OK, but the commit message should explain why they're getting reverted.
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, michael@paquier.xyz, buschmann@nidsa.net
Subject: Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode
In-Reply-To: <1075837.1629207570@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