| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Timeout failure in 019_replslot_limit.pl |
| Date: | 2021-09-06 14:59:42 |
| Message-ID: | 202109061459.bwadwxp4kf53@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | gkokolatos | 2021-09-06 15:02:50 | Re: Showing I/O timings spent reading/writing temp buffers in EXPLAIN |
| Previous Message | David G. Johnston | 2021-09-06 14:50:15 | Re: Correct handling of blank/commented lines in PSQL interactive-mode history |