Re: pg_basebackup option for handling symlinks

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_basebackup option for handling symlinks
Date: 2012-01-08 21:22:08
Message-ID: CABUevEwdxKbHDW25WSOoXgcjGwQAJTwt==5KUbsvC1nJ0Zz5yA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jan 8, 2012 at 21:53, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> I've recently had a possible need for telling pg_basebackup how to
> handle symlinks in the remote data directory, instead of ignoring them,
> which is what currently happens.  Possible options were recreating the
> symlink locally (pointing to a file on the local system) or copying the
> file the symlink points to.  This is mainly useful in scenarios where
> configuration files are symlinked from the data directory.  Has anyone
> else had the need for this?  Is it worth pursuing?

Yes.

I came up to the same issue though - in one case it would've been best
to copy the link, in the other case it would've been best to copy the
contents of the file :S Couldn't decide which was most important...
Maybe a switch would be needed?

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2012-01-08 21:32:41 Re: run check constraints only when affected columns are changed?
Previous Message Peter Eisentraut 2012-01-08 20:53:01 pg_basebackup option for handling symlinks