Michael Paquier wrote:
> Lately hamster is failing every 4/5 days on the recovery regression
> tests in 003 covering the recovery targets, with that:
> # Postmaster PID for node "standby_2" is 20510
> Timed out while waiting for standby to catch up at
> t/003_recovery_targets.pl line 36.
> Which means that poll_for_query timed out for the standby to catch up..
> Here is an example of test that failed:
Yeah, thanks, pushed. However this doesn't explain all the failures we see:
we see the pg_basebackup test failing. I suppose that failure is also
because of slowness, though of course this patch won't fix it.
we see a completely different failure:
error running SQL: 'psql:<stdin>:1: ERROR: relation "tab_int" does not exist
LINE 1: SELECT count(*) FROM tab_int
while running 'psql -XAtq -d port=52824 host=/tmp/or2xHglniM dbname=postgres -f
- -v ON_ERROR_STOP=1' at
Do we have an explanation for this one?
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Sent via pgsql-hackers mailing list (firstname.lastname@example.org)
To make changes to your subscription: