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

From Christoph Berg
Subject Re: fsync-pgdata-on-recovery tries to write to more files than previously
Date
Msg-id 20150523213641.GF28106@msg.df7cb.de
Whole thread Raw
In response to Re: fsync-pgdata-on-recovery tries to write to more files than previously  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Re: Tom Lane 2015-05-23 <2284.1432413209@sss.pgh.pa.us>
> 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.

Maybe logging WARNINGs instead of FATAL would be enough of a fix?

Christoph
--
cb@df7cb.de | http://www.df7cb.de/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Disabling trust/ident authentication configure option
Next
From: Andrew Dunstan
Date:
Subject: Re: jsonb_set: update or upsert default?