From: | Alexey Kondratov <kondratov(dot)aleksey(at)gmail(dot)com> |
---|---|
To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Supply restore_command to pg_rewind via CLI argument |
Date: | 2021-08-27 13:32:02 |
Message-ID: | CADfU8WxRZ7Td61k0tB9SyV0_SjJBaXJvs+isKvxXX_i6eDAJXQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 27, 2021 at 10:05 AM Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> There is a small bug
> + /*
> + * Take restore_command from the postgresql.conf only if it is not already
> + * provided as a command line option.
> + */
> + if (!restore_wal && restore_command == NULL)
> return;
>
> I think we should use condition (!restore_wal || restore_command != NULL).
>
Yes, you are right, thanks. Attached is a fixed version. Tests were
passing since PostgresNode->enable_restoring is adding restore_command
to the postgresql.conf anyway.
>
> Besides this patch looks good and is ready for committer IMV.
>
--
Alexey Kondratov
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Allow-providing-restore_command-as-a-command-line.patch | application/octet-stream | 11.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2021-08-27 14:00:37 | Re: [PATCH] Add OAUTH2_SCOPE variable for scope configuration |
Previous Message | Marko Tiikkaja | 2021-08-27 12:44:37 | Re: UNIQUE null treatment option |