Skip site navigation (1) Skip section navigation (2)

Re: Scanning pg_tablespace from walsender

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Scanning pg_tablespace from walsender
Date: 2011-01-03 15:52:20
Message-ID: AANLkTimUJg+8QwOQ7J3bghEP=pNb_v3e94YQ3ErE=LFJ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Jan 3, 2011 at 10:42 AM, Magnus Hagander <magnus(at)hagander(dot)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.

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

In response to

Responses

pgsql-hackers by date

Next:From: Stephen FrostDate: 2011-01-03 15:56:27
Subject: Re: Re: new patch of MERGE (merge_204) & a question about duplicated ctid
Previous:From: Tom LaneDate: 2011-01-03 15:50:11
Subject: Re: Scanning pg_tablespace from walsender

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group