Re: Allow some recovery parameters to be changed with reload - Mailing list pgsql-hackers

From Sergei Kornilov
Subject Re: Allow some recovery parameters to be changed with reload
Date
Msg-id 108021604695421@mail.yandex.ru
Whole thread Raw
In response to Re: Allow some recovery parameters to be changed with reload  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: Allow some recovery parameters to be changed with reload  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Re: Allow some recovery parameters to be changed with reload  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
Hello

> I'm wondering if it's safe to allow restore_command to be emptied during
> archive recovery. Even when it's emptied, archive recovery can proceed
> by reading WAL files from pg_wal directory. This is the same behavior as
> when restore_command is set to, e.g., /bin/false.

I am always confused by this implementation detail. restore_command fails? Fine, let's just read file from pg_wal. But
thisis different topic...
 

I do not know the history of this fatal ereport. It looks like "must specify restore_command when standby mode is not
enabled"check is only intended to protect the user from misconfiguration and the rest code will treat empty
restore_commandcorrectly, just like /bin/false. Did not notice anything around StandbyMode conditions.
 

regards, Sergei



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: re: pgbench stopped supporting large number of client connections on Windows
Next
From: Fabien COELHO
Date:
Subject: Re: pgbench stopped supporting large number of client connections on Windows