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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode
Дата
Msg-id 1075837.1629207570@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode  (Bruce Momjian <bruce@momjian.us>)
Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
Дерево обсуждения 
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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: ALTER TYPE vs extension membership (was Re: BUG #17144: Upgrade from v13 to v14 with the cube extension failed)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: A problem in ExecModifyTable