From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SSL information view |
Date: | 2014-07-16 10:22:56 |
Message-ID: | CABUevEwqFr3Yv=ePwJnJj0DtQ+wTom4Ts711M83uf9H8HaVYJQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 14, 2014 at 7:54 PM, Stefan Kaltenbrunner
<stefan(at)kaltenbrunner(dot)cc> wrote:
> On 07/13/2014 10:35 PM, Magnus Hagander wrote:
>> On Sun, Jul 13, 2014 at 10:32 PM, Stefan Kaltenbrunner
>> <stefan(at)kaltenbrunner(dot)cc> wrote:
>>> On 07/12/2014 03:08 PM, Magnus Hagander wrote:
>>>> As an administrator, I find that you fairly often want to know what
>>>> your current connections are actually using as SSL parameters, and
>>>> there is currently no other way than gdb to find that out - something
>>>> we definitely should fix.
>>>
>>> Yeah that would be handy - however I often wish to be able to figure
>>> that out based on the logfile as well, any chance of getting these into
>>> connection-logging/log_line_prefix as well?
>>
>> We do already log some of it if you have enabled log_connections -
>> protocol and cipher. Anything else in particular you'd be looking for
>> - compression info?
>
> DN mostly, not sure I care about compression info...
Compression fitted more neatly in with the format that was there now.
I wonder if we shuold add a DETAIL field on that error message that
has the DN in case there is a client certificate. Would that make
sense?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2014-07-16 10:31:59 | Re: [bug fix] pg_ctl always uses the same event source |
Previous Message | Amit Kapila | 2014-07-16 10:03:39 | Re: better atomics - v0.5 |