Quick Links

Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode

From:	Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:	Michael Paquier <michael(at)paquier(dot)xyz>
Cc:	Hans Buschmann <buschmann(at)nidsa(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject:	Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode
Date:	2021-08-17 13:39:30
Message-ID:	1075837.1629207570@sss.pgh.pa.us
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

Michael Paquier <michael(at)paquier(dot)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

In response to

Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode at 2021-08-17 02:00:47 from Michael Paquier

Responses

Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode at 2021-08-17 15:26:29 from Bruce Momjian
Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode at 2021-08-18 00:14:14 from Michael Paquier

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Tom Lane	2021-08-17 14:13:55	Re: A problem in ExecModifyTable
Previous Message	Tom Lane	2021-08-17 13:35:50	Re: ALTER TYPE vs extension membership (was Re: BUG #17144: Upgrade from v13 to v14 with the cube extension failed)