Re: libpq debug log - Mailing list pgsql-hackers

From Andres Freund
Subject Re: libpq debug log
Date
Msg-id 20190214181616.nj7sorzudylh4sx2@alap3.anarazel.de
Whole thread Raw
In response to Re: libpq debug log  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: libpq debug log  (Jacob Champion <pchampion@pivotal.io>)
RE: libpq debug log  ("Jamison, Kirk" <k.jamison@jp.fujitsu.com>)
List pgsql-hackers
Hi,

On 2018-11-28 23:20:03 +0100, Peter Eisentraut wrote:
> This does not excite me.  It seems mostly redundant with using tcpdump.

I think the one counter-argument to this is that using tcpdump in
real-world scenarios has become quite hard, due to encryption. Even with
access to the private key you cannot decrypt the stream.  Wonder if the
solution to that would be an option to write out the decrypted data into
a .pcap or such.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Oleksii Kliukin
Date:
Subject: Re: Per-tablespace autovacuum settings
Next
From: Andres Freund
Date:
Subject: Re: \describe*