Re: initdb -S and tablespaces - Mailing list pgsql-hackers

From Robert Haas
Subject Re: initdb -S and tablespaces
Date
Msg-id CA+TgmoZ=nm5wZG3gNPydmfGZoDH8zgUKbUvFOBi9JKQ6jTUhCg@mail.gmail.com
Whole thread Raw
In response to Re: initdb -S and tablespaces  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: initdb -S and tablespaces  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Apr 30, 2015 at 6:44 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Robert Haas wrote:
>> On Thu, Apr 30, 2015 at 6:18 PM, Alvaro Herrera
>> <alvherre@2ndquadrant.com> wrote:
>> >> Also, it seems awfully unfortunate to me that we're duplicating a
>> >> whole pile of code into xlog.c here.  Maybe there's no way to avoid
>> >> the code duplication, but pre_sync_fname() seems like it'd more
>> >> naturally go in fd.c than here.  I dunno where walkdir should go, but
>> >> again, not in xlog.c.
>> >
>> > Hm, there's an interest in backpatching this as a bugfix, if I
>> > understand correctly; hence the duplicated code.  We could remove the
>> > duplicity later with a refactoring patch in master only.
>>
>> That seems pretty silly.  If we going to add pre_sync_fname() to every
>> branch, we should add it to the same (correct) file in all of them,
>> not put it in xlog.c in the back-branches and fd.c in master.
>
> Ah, so that's not the duplicate code that I was remembering -- I think
> it's walkdir() or something like that, which is in initdb IIRC.

Yeah, walkdir() is there too.  But if we're going to add that to the
backend, I think it should go in src/backend/storage/file, not
src/backend/access/transam.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Broken handling of NULLs in TG_ARGV
Next
From: Robert Haas
Date:
Subject: Re: Use outerPlanState() consistently in executor code