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

From Tom Lane
Subject Re: initdb -S and tablespaces
Date
Msg-id 37007.1430438177@sss.pgh.pa.us
Whole thread Raw
In response to Re: initdb -S and tablespaces  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: initdb -S and tablespaces  (Abhijit Menon-Sen <ams@2ndQuadrant.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Apr 30, 2015 at 6:44 PM, Alvaro Herrera
> <alvherre@2ndquadrant.com> wrote:
>> 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.

Agreed that .../transam is a pretty horrid choice; but maybe we should
be thinking about putting it in src/common, so there's only one copy?

As for the notion that this needs to be back-patched, I would say no.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Use outerPlanState() consistently in executor code
Next
From: Tom Lane
Date:
Subject: Re: Use outerPlanState() consistently in executor code