From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: tablespaces inside $PGDATA considered harmful |
Date: | 2017-10-07 22:10:41 |
Message-ID: | c4d3b72f-3817-862c-1412-3ea0b033f133@catalyst.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-10-07 23:22:08 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
Previous Message | Jack Christensen | 2017-10-07 21:56:26 | Prepared statements assume text type in PG10 |