Re: pgsql: Re-enable TAP tests of pg_receivewal for ZLIB on Windows - Mailing list pgsql-committers

From Michael Paquier
Subject Re: pgsql: Re-enable TAP tests of pg_receivewal for ZLIB on Windows
Date
Msg-id YPdfuyUga6yMPOqX@paquier.xyz
Whole thread Raw
In response to Re: pgsql: Re-enable TAP tests of pg_receivewal for ZLIB on Windows  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pgsql: Re-enable TAP tests of pg_receivewal for ZLIB on Windows  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-committers
On Tue, Jul 20, 2021 at 05:33:52PM -0400, Andrew Dunstan wrote:
> fairywren doesn't seem to like this.

Indeed, it doesn't.  The logs don't offer much, and I am not sure if
this is a problem that happens when opening the first segment, or if
that's the first write.  The starting position is good:
pg_receivewal: starting log streaming at 0/2000000 (timeline 1)

fairywren did not run the first round of those tests in ffc9dda,
perhaps that's a different issue than what bowerbird has reported.

The backend logs don't tell much either, but that certainly looks like
a crash:
2021-07-20 15:33:30.684 UTC [59784:13] 020_pg_receivewal.pl STATEMENT:
START_REPLICATION 0/2000000 TIMELINE 1
2021-07-20 15:33:30.793 UTC [59784:14] 020_pg_receivewal.pl LOG:
could not receive data from client: An existing connection was
forcibly closed by the remote host.
2021-07-20 15:33:30.793 UTC [59784:15] 020_pg_receivewal.pl STATEMENT:
START_REPLICATION 0/2000000 TIMELINE 1
2021-07-20 15:33:30.793 UTC [59784:16] 020_pg_receivewal.pl LOG:
unexpected EOF on standby connection

Could it be possible to get a backtrace?  I won't let this enabled
much longer, just waiting for bowerbird to tell more.
--
Michael

Attachment

pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: pgsql: doc: PG 14 relnote adjustments
Next
From: Fujii Masao
Date:
Subject: pgsql: Make XLOG_FPI_FOR_HINT records honor full_page_writes setting.