Re: Moving other hex functions to /common

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Sehrope Sarkuni <sehrope(at)jackdb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Moving other hex functions to /common
Date: 2021-01-14 03:11:54
Message-ID: 1364545.1610593914@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2021-01-14 03:34:01 Re: A failure of standby to follow timeline switch
Previous Message Masahiko Sawada 2021-01-14 03:08:28 Re: Executing inet_server_addr/port() in parallel workers