| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-24 09:04:04 |
| Message-ID: | 20150524090404.GA28553@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: To Andres Freund 2015-05-24 <20150524075244(dot)GB27048(at)msg(dot)df7cb(dot)de>
> Re: Andres Freund 2015-05-24 <20150524005245(dot)GD32396(at)alap3(dot)anarazel(dot)de>
> > How about, to avoid masking actual problems, we have a more
> > differentiated logic for the toplevel data directory? I think we could
> > just skip all non-directory files in there data_directory itself. None
> > of the files in the toplevel directory, with the exception of
> > postgresql.auto.conf, will ever get written to by PG itself. And if
> > there's readonly files somewhere in a subdirectory, I won't feel
> > particularly bad.
pg_log/ is also admin domain. What about only recursing into
well-known directories + postgresql.auto.conf?
(I've also been wondering if pg_basebackup shouldn't skip pg_log, but
that's a different topic...)
Christoph
--
cb(at)df7cb(dot)de | http://www.df7cb.de/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nils Goroll | 2015-05-24 11:42:57 | Re: xid wrap / optimize frozen tables? |
| Previous Message | Christoph Berg | 2015-05-24 07:52:44 | Re: fsync-pgdata-on-recovery tries to write to more files than previously |