Re: Scanning pg_tablespace from walsender - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Scanning pg_tablespace from walsender
Date
Msg-id 20218.1294071266@sss.pgh.pa.us
Whole thread Raw
In response to Re: Scanning pg_tablespace from walsender  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Scanning pg_tablespace from walsender  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Jan 3, 2011 at 10:42 AM, Magnus Hagander <magnus@hagander.net> wrote:
>> Well, they need to be put back in the same location on the other
>> machine (slave in case of replication, tarball otherwise). If I just
>> traverse the symlinks, they'll just appears as a subdirectory of
>> pg_tblspc on the other machine, won't they?

> Sure, I guess you'd need to read the links if you want it to work that way.

Well, you're quietly ignoring a whole bunch of issues there, like
whether the tablespaces *should* be in the identical locations on the
other machine and how you'll deal with it if not.  Eventually there's
going to need to be some sort of "tablespace mapping" option for
replication.  But anyway, taking a base backup is fundamentally defined
as "scan the filesystem, paying no attention to catalogs" and ISTM that
it obviously should be the same way for tablespaces.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Re: new patch of MERGE (merge_204) & a question about duplicated ctid
Next
From: Magnus Hagander
Date:
Subject: Re: Scanning pg_tablespace from walsender