Re: libpq debug log

From: "alvherre(at)alvh(dot)no-ip(dot)org" <alvherre(at)alvh(dot)no-ip(dot)org>
To: "iwata(dot)aya(at)fujitsu(dot)com" <iwata(dot)aya(at)fujitsu(dot)com>
Cc: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>, 'Kyotaro Horiguchi' <horikyota(dot)ntt(at)gmail(dot)com>, "k(dot)jamison(at)fujitsu(dot)com" <k(dot)jamison(at)fujitsu(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: libpq debug log
Date: 2021-02-24 01:40:32
Message-ID: 20210224014032.GA20620@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

I'll give this another look tomorrow, but I wanted to pass along that I
prefer libpq-trace.{c,h} instead of libpq-logging. I also renamed
variable "pin" and pgindented. I don't have any major reservations
about this patch now, so I'll mark it ready-for-committer in case
somebody else wants to have a look before push.

(Not sure about the use of the word "forcely")

Álvaro Herrera 39°49'30"S 73°17'W

Attachment Content-Type Size
v20-0001-Improve-libpq-tracing-capabilities.patch text/x-diff 33.1 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message 2021-02-24 01:42:57 Refactor ECPGconnect and allow IPv6 connection
Previous Message Jacob Champion 2021-02-24 00:11:55 Re: Support for NSS as a libpq TLS backend