Re: [PATCH] Log details for client certificate failures

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [PATCH] Log details for client certificate failures
Дата
Msg-id 6f9eff5c-ecc6-c0d5-df8e-8df9e2f10534@enterprisedb.com
обсуждение исходный текст
Ответ на Re: [PATCH] Log details for client certificate failures  (Jacob Champion <jchampion@timescale.com>)
Ответы Re: [PATCH] Log details for client certificate failures  (Jacob Champion <jchampion@timescale.com>)
Re: [PATCH] Log details for client certificate failures  (Masahiko Sawada <sawada.mshk@gmail.com>)
Список pgsql-hackers
Дерево обсуждения 
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 по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c)
Следующее
От: Matthias van de Meent
Дата:
Сообщение: Re: Tuples inserted and deleted by the same transaction