From: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
---|---|
To: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
Cc: | Crisp Lee <litianxiang01(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us> |
Subject: | Re: make pg_ctl more friendly |
Date: | 2024-01-09 13:22:49 |
Message-ID: | CAN55FZ2xFfVKFaYEf9_ygsF9hr7SyN3MiXZ9vep1oKC=AkCpuw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Thank you for working on this! I agree that the current message is not friendly.
On Thu, 9 Nov 2023 at 10:19, Junwang Zhao <zhjwpku(at)gmail(dot)com> wrote:
>
> On Thu, Nov 9, 2023 at 3:08 PM Junwang Zhao <zhjwpku(at)gmail(dot)com> wrote:
> >
> > After a PITR shutdown, the db state should be *shut down in recovery*, try the
> > patch attached.
> >
>
> previous patch has some format issues, V2 attached.
v2-0001-PITR-shutdown-should-not-report-error-by-pg_ctl.patch:
- "Examine the log output.\n"),
+ "Examine the log output\n"),
progname);
I don't think that this is needed.
Other than that, the patch looks good and I confirm that after PITR shutdown:
"PITR shutdown"
"update configuration for startup again if needed"
message shows up, instead of:
"pg_ctl: could not start server"
"Examine the log output.".
nitpick: It would be better if the order of the error message cases
and enums is the same ( i.e. 'POSTMASTER_RECOVERY_SHUTDOWN' before
'POSTMASTER_FAILED' in enum )
--
Regards,
Nazir Bilal Yavuz
Microsoft
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2024-01-09 14:03:39 | Re: add AVX2 support to simd.h |
Previous Message | Amit Kapila | 2024-01-09 13:09:43 | Re: Synchronizing slots from primary to standby |