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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Re-enable TAP tests of pg_receivewal for ZLIB on Windows
Date: 2021-07-20 23:43:55
Message-ID: YPdfuyUga6yMPOqX@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2021-07-21 02:19:49 pgsql: Make XLOG_FPI_FOR_HINT records honor full_page_writes setting.
Previous Message Bruce Momjian 2021-07-20 23:37:34 pgsql: doc: PG 14 relnote adjustments