Re: [GENERAL] Permission Denied Error on pg_xlog/RECOVERYXLOG file - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [GENERAL] Permission Denied Error on pg_xlog/RECOVERYXLOG file
Date
Msg-id CA+TgmobsnLKgtVHiX7VRT30JnGb5bfy_GdmPwr+P3Hikrf2gOQ@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] Permission Denied Error on pg_xlog/RECOVERYXLOG file  (Andres Freund <andres@anarazel.de>)
Responses Re: [GENERAL] Permission Denied Error on pg_xlog/RECOVERYXLOG file  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Fri, May 27, 2016 at 8:44 PM, Andres Freund <andres@anarazel.de> wrote:
> I'm not convinced of that.  Hiding unexpected issues for longer, just to
> continue kind-of-operating, can make the impact of problems a lot worse,
> and it makes it very hard to actually learn about the issues.

So if we made this a WARNING rather than an ERROR, it wouldn't hiding
the issue, but it would be less likely to break things that worked
before.  No?

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PostmasterPid not marked with PGDLLIMPORT
Next
From: Robert Haas
Date:
Subject: Re: Change in order of criteria - reg