Re: Timeout failure in 019_replslot_limit.pl - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Timeout failure in 019_replslot_limit.pl
Date
Msg-id 202109061459.bwadwxp4kf53@alvherre.pgsql
Whole thread Raw
In response to Timeout failure in 019_replslot_limit.pl  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Timeout failure in 019_replslot_limit.pl  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hello

On 2021-Sep-06, Michael Paquier wrote:

> Running the recovery tests in a parallel run, enough to bloat a
> machine in resources, sometimes leads me to the following failure:
> ok 19 - walsender termination logged
> # poll_query_until timed out executing this query:
> # SELECT wal_status FROM pg_replication_slots WHERE slot_name = 'rep3'

Hmm, I've never seen that, and I do run tests in parallel quite often.
Would you please attach the log files for that test in a failed run?

-- 
Álvaro Herrera              Valdivia, Chile  —  https://www.EnterpriseDB.com/
"This is what I like so much about PostgreSQL.  Most of the surprises
are of the "oh wow!  That's cool" Not the "oh shit!" kind.  :)"
Scott Marlowe, http://archives.postgresql.org/pgsql-admin/2008-10/msg00152.php



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Correct handling of blank/commented lines in PSQL interactive-mode history
Next
From: gkokolatos@pm.me
Date:
Subject: Re: Showing I/O timings spent reading/writing temp buffers in EXPLAIN