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 [email protected]
Whole thread Raw
In response to Re: fsync-pgdata-on-recovery tries to write to more files than previously  (Christoph Berg <[email protected]>)
Responses Re: fsync-pgdata-on-recovery tries to write to more files than previously
List pgsql-hackers
Re: To Andres Freund 2015-05-24 <[email protected]>
> Re: Andres Freund 2015-05-24 <[email protected]>
> > 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
-- 
[email protected] | http://www.df7cb.de/



pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: fsync-pgdata-on-recovery tries to write to more files than previously
Next
From: Nils Goroll
Date:
Subject: Re: xid wrap / optimize frozen tables?