Re: Supply restore_command to pg_rewind via CLI argument - Mailing list pgsql-hackers

From Alexey Kondratov
Subject Re: Supply restore_command to pg_rewind via CLI argument
Date
Msg-id CADfU8WxRZ7Td61k0tB9SyV0_SjJBaXJvs+isKvxXX_i6eDAJXQ@mail.gmail.com
Whole thread Raw
In response to Re: Supply restore_command to pg_rewind via CLI argument  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: Supply restore_command to pg_rewind via CLI argument  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
On Fri, Aug 27, 2021 at 10:05 AM Andrey Borodin <x4mmm@yandex-team.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

pgsql-hackers by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: UNIQUE null treatment option
Next
From: Daniel Gustafsson
Date:
Subject: Re: [PATCH] Add OAUTH2_SCOPE variable for scope configuration