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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Michael Paquier <michael@paquier.xyz>

Cc: Hans Buschmann <buschmann@nidsa.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2021-08-17T13:39:30Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Revert refactoring of hex code to src/common/
- 1900c140554e 14.0 landed
- 2576dcfb76aa 15.0 landed
Rework refactoring of hex and encoding routines
- aef8948f38d9 14.0 cited

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