Re: libpq debug log - Mailing list pgsql-hackers

From Robert Haas
Subject Re: libpq debug log
Date
Msg-id CA+TgmoYQNZm_DquU6wOd2NB13qrAMQ5vhd1P0Ggv0N3+khE8qQ@mail.gmail.com
Whole thread Raw
In response to Re: libpq debug log  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: libpq debug log
List pgsql-hackers
On Fri, Aug 24, 2018 at 9:48 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> PQtrace() is utterly useless for anything except debugging libpq
> internals, and it's not tremendously useful even for that.  Don't
> bother with that part.

I think that improving the output format could help with that a lot.
What it current produces is almost unreadable; adjusting it to emit
one line per protocol message would, I think, help a lot.  There are
probably other improvements that could be made at the same time.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump --load-via-partition-root vs. parallel restore
Next
From: Tom Lane
Date:
Subject: Re: libpq debug log