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

From Andres Freund
Subject Re: fsync-pgdata-on-recovery tries to write to more files than previously
Date
Msg-id 20150525174148.GK32396@alap3.anarazel.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>)
Responses Re: fsync-pgdata-on-recovery tries to write to more files than previously
List pgsql-hackers
On 2015-05-25 13:38:01 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On May 24, 2015 7:52:53 AM PDT, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > If we'd merge it with initdb's list I think I'd not be that bad. I'm thinking of some header declaring it, roughly
likethe rmgr list.
 
> 
> pg_log/ is a counterexample to that idea too; initdb doesn't know about it
> (and shouldn't).

The idea would be to *only* directories that initdb knows about. Since
that's where the valuables are. So I don't see how pg_log would be a
counterexample.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: fsync-pgdata-on-recovery tries to write to more files than previously
Next
From: Stephen Frost
Date:
Subject: Re: fsync-pgdata-on-recovery tries to write to more files than previously