| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: fsync-pgdata-on-recovery tries to write to more files than previously |
| Date: | 2015-05-23 21:36:41 |
| Message-ID: | 20150523213641.GF28106@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: Tom Lane 2015-05-23 <2284(dot)1432413209(at)sss(dot)pgh(dot)pa(dot)us>
> Christoph Berg <myon(at)debian(dot)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(at)df7cb(dot)de | http://www.df7cb.de/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2015-05-23 22:01:06 | Re: jsonb_set: update or upsert default? |
| Previous Message | Tom Lane | 2015-05-23 21:15:32 | Re: Disabling trust/ident authentication configure option |