Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode
От
Michael Paquier
Тема
Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode
Дата
Msg-id
YRxP6KWGfFRTnxCm@paquier.xyz
Ответ на
Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode (Julien Rouhaud)
Список
Дерево обсуждения
PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode Hans Buschmann <buschmann@nidsa.net>
Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode Ranier Vilela <ranier.vf@gmail.com>
AW: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode Hans Buschmann <buschmann@nidsa.net>
Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode Ranier Vilela <ranier.vf@gmail.com>
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 Ranier Vilela <ranier.vf@gmail.com>
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 Tom Lane <tgl@sss.pgh.pa.us>
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 Julien Rouhaud <rjuju123@gmail.com>
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 Michael Paquier <michael@paquier.xyz>
Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode Michael Paquier <michael@paquier.xyz>
On Wed, Aug 18, 2021 at 12:34:45AM +0800, Julien Rouhaud wrote: > On Tue, Aug 17, 2021 at 11:26 PM Bruce Momjian wrote: >> Uh, I don't see those commits, e.g.: >> >> $ git diff 0d70d30 >> fatal: ambiguous argument '0d70d30': unknown revision or path not in the working tree. >> Use '--' to separate paths from revisions, like this: >> 'git [...] -- [...]' >> >> $ git diff 5c33ba5 >> fatal: ambiguous argument '5c33ba5': unknown revision or path not in the working tree. >> Use '--' to separate paths from revisions, like this: >> 'git [...] -- [...]' >> >> $ git diff 92436a7 >> fatal: ambiguous argument '92436a7': unknown revision or path not in the working tree. >> Use '--' to separate paths from revisions, like this: >> 'git [...] -- [...]' > > Same here. I'm assuming that the real commits are the one mentioned > in the patch, which are c3826f8, aef8948 and ccf4e27. Oops, incorrect copy-paste from my side. Yes, the commits impacted here are aef8948, ccf4e27 and c3826f8. The small-ish commit message of the patch got thet right. -- Michael
В списке pgsql-hackers по дате отправления
От: Michael Paquier
Дата: