On 26/09/17 20:44, Mark Kirkwood wrote:
$ pg_basebackup -D .
WARNING: could not read symbolic link "pg_tblspc/space1": Invalid
argument
pg_basebackup: directory "/data0/pgdata/11/pg_tblspc/space1" exists
but is not empty
pg_basebackup: removing contents of data directory "."
Err - actually this example is wrong - sorry. In fact pg_basebackup is
complaining because it does not want to overwrite the contents of the
tablespace (need to use the -T option as I'm on the same host)!
A correct example of pg_basebackup failing due to tablespaces inside
$PGDATA/pg_tblspc can be easily demonstrated by trying to set up
streaming replication on another host:
$ pg_basebackup -h 10.0.119.100 -P -D .
WARNING: could not read symbolic link "pg_tblspc/space1": Invalid argument
pg_basebackup: could not create directory "./pg_tblspc": File exists
Fortunately this can be worked around by changing to tar format:
$ pg_basebackup -h 10.0.119.100 -Ft -P -D .
WARNING: could not read symbolic link "pg_tblspc/space1": Invalid argument
1560632/1560632 kB (100%), 2/2 tablespaces
...however, not that great that the plain mode is busted.
regards
Mark
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
