Postgres Pro
Downloads
Home   >   mailing lists

Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode
Date
Msg-id 1075837.1629207570@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode  (Michael Paquier <michael@paquier.xyz>)
Responses Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode
Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ALTER TYPE vs extension membership (was Re: BUG #17144: Upgrade from v13 to v14 with the cube extension failed)
Next
From: Tom Lane
Date:
Subject: Re: A problem in ExecModifyTable