RE: libpq debug log - Mailing list pgsql-hackers

From iwata.aya@fujitsu.com
Subject RE: libpq debug log
Date
Msg-id TY2PR01MB19636A6487242EE18E719DEEEA7A9@TY2PR01MB1963.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: libpq debug log  ("'alvherre@alvh.no-ip.org'" <alvherre@alvh.no-ip.org>)
Responses Re: libpq debug log
List pgsql-hackers
Hi Alvaro san

Thank you for your fix of trace log code.

> From: 'alvherre@alvh.no-ip.org' <alvherre@alvh.no-ip.org>
> Sent: Friday, April 2, 2021 11:30 AM
...
> It still didn't fix it!  Drongo is now reporting a difference in the expected trace --
> and the differences all seem to be message lengths.
> Now that is pretty mysterious, because the messages themselves are printed
> identically.  Perl's output is pretty unhelpful, but I wrote them to a file and diffed
> manually; it's attached.

Do ErrorResponse and NoticeResponse vary from test to test ...?
If so, it seemed difficult to make the trace logs available for regression test. 
I will also investigate the cause of this issue.

Regards,
Aya Iwata

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: TRUNCATE on foreign table
Next
From: Masahiko Sawada
Date:
Subject: Re: Flaky vacuum truncate test in reloptions.sql