| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | recoveryCheck test failure on flaviventris |
| Date: | 2025-04-16 02:54:58 |
| Message-ID: | CAMbWs4_HSzYsOXfn+BPFQoN7bp7ff_+h=fcvfBN7aLJ=3Hf_Dg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2025-04-16 03:05:57 | Re: recoveryCheck test failure on flaviventris |
| Previous Message | Mahendra Singh Thalor | 2025-04-16 02:53:28 | Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore |