Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #16003: pg_basebackup failed with error : directory"xxxxxxx" exists but is not empty - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #16003: pg_basebackup failed with error : directory"xxxxxxx" exists but is not empty
Date
Msg-id 20190913034241.GC2285@paquier.xyz
Whole thread Raw
In response to Re: BUG #16003: pg_basebackup failed with error : directory "xxxxxxx"exists but is not empty  (Magnus Hagander <magnus@hagander.net>)
List pgsql-bugs
Tree view 
On Thu, Sep 12, 2019 at 09:27:02AM -0400, Magnus Hagander wrote:
> And actually putting new tablespace directories inside other tablespaces is
> *definitely* not the way it's supposed to be done.

Yes.

> As a workaround, you might be able to use pg_basebackup with -T to relocate
> the tablespaces into a directory that is not in conflict.

I was wondering about that and that should work.  Looking at sendDir()
in basebackup.c, we only accept links from the root of pg_tlbspc, so
all any links inside another tablespace would just be ignored.  In
this case, the server would complain with a WARNING and "skipping
special file blah".
--
Michael
Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg
Next
From: Vinay Banakar
Date:
Subject: Re: BUG #16006: Update queries fail on a table having any policy witha function that takes a whole-row var as arg