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

From Andres Freund
Subject Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location
Date
Msg-id 20160414151221.dst4gxpnfrtyw5rq@alap3.anarazel.de
Whole thread Raw
In response to pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location  (Ashutosh Sharma <ashu.coek88@gmail.com>)
Responses Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location  (Ashutosh Sharma <ashu.coek88@gmail.com>)
Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
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: Alexander Korotkov
Date:
Subject: Re: [HACKERS] Re: pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <
Next
From: Tom Lane
Date:
Subject: Re: Why doesn't src/backend/port/win32/socket.c implement bind()?