Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Log details for client certificate failures - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Log details for client certificate failures
Date
Msg-id 6f9eff5c-ecc6-c0d5-df8e-8df9e2f10534@enterprisedb.com
Whole thread Raw
In response to Re: [PATCH] Log details for client certificate failures  (Jacob Champion <jchampion@timescale.com>)
Responses Re: [PATCH] Log details for client certificate failures
Re: [PATCH] Log details for client certificate failures
List pgsql-hackers
Tree view 
On 09.09.22 00:32, Jacob Champion wrote:
> On Thu, Jul 28, 2022 at 9:19 AM Jacob Champion <jchampion@timescale.com> wrote:
>> On Thu, Jul 21, 2022 at 4:29 PM Jacob Champion <jchampion@timescale.com> wrote:
>>> v4 attempts to fix this by letting the check hooks pass
>>> MCXT_ALLOC_NO_OOM to pg_clean_ascii(). (It's ignored in the frontend,
>>> which just mallocs.)
>>
>> Ping -- should I add an open item somewhere so this isn't lost?
> 
> Trying again. Peter, is this approach acceptable? Should I try something else?

This looks fine to me.  Committed.

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c)
Next
From: Matthias van de Meent
Date:
Subject: Re: Tuples inserted and deleted by the same transaction