Re: could not stat promote trigger file leads to shutdown

On Thu, Nov 14, 2019 at 10:58 PM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
>
> I have seen the error
>
>      could not stat promote trigger file "...": Permission denied
>
> because of a misconfiguration (for example, setting promote_trigger_file
> to point into a directory to which you don't have appropriate read or
> execute access).
>
> The problem is that because this happens in the startup process, the
> ERROR is turned into a FATAL and the whole instance shuts down.  That
> seems like a harsh penalty.  Would it be better to turn this ERROR into
> a WARNING?

+1

Regards,

-- 
Fujii Masao