Re: shouldn't we log permission errors when accessing the configured trigger file? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: shouldn't we log permission errors when accessing the configured trigger file?
Date
Msg-id CA+TgmoYBWbtVV6R2ALhy1gqZgKDiWhiWiQLPmT1v--Dt--UZsg@mail.gmail.com
Whole thread Raw
In response to shouldn't we log permission errors when accessing the configured trigger file?  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: shouldn't we log permission errors when accessing the configured trigger file?  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Sun, Jan 26, 2014 at 1:03 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> For some reason CheckForStandbyTrigger() doesn't report permission
> errors when stat()int the trigger file. Shouldn't we fix that?
>
> static bool
> CheckForStandbyTrigger(void)
> {
> ...
>         if (stat(TriggerFile, &stat_buf) == 0)
>         {
>                 ereport(LOG,
>                                 (errmsg("trigger file found: %s", TriggerFile)));
>                 unlink(TriggerFile);
>                 triggered = true;
>                 fast_promote = true;
>                 return true;
>         }
>
> Imo the stat() should warn about all errors but ENOENT?

Seems reasonable.  It could lead to quite a bit of log spam, I
suppose, but the way things are now could be pretty mystifying if
you've located your trigger file somewhere outside $PGDATA, and a
parent directory is lacking permissions.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Race condition in b-tree page deletion
Next
From: Magnus Hagander
Date:
Subject: Re: shouldn't we log permission errors when accessing the configured trigger file?