recoveryCheck test failure on flaviventris - Mailing list pgsql-hackers

From Richard Guo
Subject recoveryCheck test failure on flaviventris
Date
Msg-id CAMbWs4_HSzYsOXfn+BPFQoN7bp7ff_+h=fcvfBN7aLJ=3Hf_Dg@mail.gmail.com
Whole thread Raw
Responses Re: recoveryCheck test failure on flaviventris
List pgsql-hackers
I noticed this recoveryCheck test failure on flaviventris after
pushing commit 3b35f9a4c (Fix an incorrect check in get_memoize_path).

### Reloading node "standby"
# Running: pg_ctl --pgdata xxx/pgdata reload
server signaled
### Restarting node "standby"
# Running: pg_ctl --wait --pgdata xxx/pgdata --log xxx.log restart
waiting for server to shut down ... failed
pg_ctl: server does not shut down
# pg_ctl restart failed; see logfile for details: xxx.log
# Postmaster PID for node "standby" is 63577
[02:09:29.767](364.847s) Bail out!  pg_ctl restart failed

I'm not convinced this failure is related to 3b35f9a4c; it seems
unlikely that just changing how Memoize paths are created would cause
it.

Does anyone have any insights into what might be going on?

Thanks
Richard



pgsql-hackers by date:

Previous
From: Mahendra Singh Thalor
Date:
Subject: Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore
Next
From: Richard Guo
Date:
Subject: Re: recoveryCheck test failure on flaviventris