| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: could not stat promote trigger file leads to shutdown |
| Date: | 2019-11-14 14:22:01 |
| Message-ID: | CAHGQGwHPkeP1DqygnbfJ=bhDwrqOOssf+w1er1W8Qrf8wT512Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 14, 2019 at 10:58 PM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2019-11-14 14:47:57 | Re: segfault in geqo on experimental gcc animal |
| Previous Message | Fujii Masao | 2019-11-14 14:14:22 | Re: Allow CREATE OR REPLACE VIEW to rename the columns |