Re: fsync-pgdata-on-recovery tries to write to more files than previously - Mailing list pgsql-hackers

From Tom Lane
Subject Re: fsync-pgdata-on-recovery tries to write to more files than previously
Date
Msg-id 2284.1432413209@sss.pgh.pa.us
Whole thread Raw
In response to fsync-pgdata-on-recovery tries to write to more files than previously  (Christoph Berg <myon@debian.org>)
Responses Re: fsync-pgdata-on-recovery tries to write to more files than previously  (Christoph Berg <myon@debian.org>)
Re: fsync-pgdata-on-recovery tries to write to more files than previously  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Christoph Berg <myon@debian.org> writes:
> the new fsync-pgdata-on-recovery code tries to open all files using
> O_RDWR. At least on 9.1, this can make recovery fail:

Hm.  I wonder whether it would be all right to just skip files for which
we get EPERM on open().  The argument being that if we can't write to the
file, we should not be held responsible for fsync'ing it either.  But
I'm not sure whether EPERM would be the only relevant errno, or whether
there are cases where this would mask real problems.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Allow GiST distance function to return merely a lower-bound.
Next
From: Tom Lane
Date:
Subject: Re: Disabling trust/ident authentication configure option