Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location - Mailing list pgsql-hackers

From Ashutosh Sharma
Subject Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location
Date
Msg-id CAE9k0P=HJQuYJr+6H0viRCPnozjvQQoa_qENYbwRzdudBVFA9Q@mail.gmail.com
Whole thread Raw
In response to Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location  (Andres Freund <andres@anarazel.de>)
Responses Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Hi,

I was just curious to know how would "pg_basebackup" behave if we do create a symbolic link for directories other than pg_xlog/pg_tblspc. However it is clearly mentioned in the documentation of pg_basebackup that if a  Symbolic link for the directories other than pg_tblspc and pg_xlog is created then it would be skipped. But, that is not the case for pg_replslot and pg_stat_tmp. Is this not an issue. Should these directories not be skipped. Please let me know your thoughts on this. Thanks.

With Regards,
Ashutosh Sharma
EnterpriseDB: http://www.enterprisedb.com

On Thu, Apr 14, 2016 at 8:42 PM, Andres Freund <andres@anarazel.de> wrote:
Hi,

On 2016-04-14 13:43:34 +0530, Ashutosh Sharma wrote:
> I tried performing pg_basebackup after creating a symbolic link for
> pg_replslot, pg_stat_tmp, pg_log and pg_clog in the source directory

That's not supported, and I strongly suspect that you're goint to hit
more than just this issue.  The only directory you're allowed to symlink
away is pg_xlog.

What were you actually trying to achieve?

Greetings,

Andres Freund

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Pglogical questions and problems
Next
From: Magnus Hagander
Date:
Subject: Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location