Re: Moving other hex functions to /common

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

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

To: Bruce Momjian <bruce@momjian.us>

Cc: Michael Paquier <michael@paquier.xyz>, Sehrope Sarkuni <sehrope@jackdb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2021-01-14T03:11:54Z

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 →

Rework refactoring of hex and encoding routines
- aef8948f38d9 14.0 landed

Bruce Momjian <bruce@momjian.us> writes:
> On Thu, Jan 14, 2021 at 11:17:40AM +0900, Michael Paquier wrote:
>> Thanks, Sehrope.  I have reviewed the code this morning and fixed
>> that, adjusted a couple of elog() strings I found inconsistent after
>> review and ran pgindent.  And applied it.

> Thanks.  All my key management regression tests pass on top of your
> applied patch.

Should the CF entry for this be closed?  The cfbot is still trying to
apply the patch, and unsurprisingly failing.

			regards, tom lane