| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PG Bug reporting form <noreply(at)postgresql(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org, sebastien(dot)ruiz(at)harmonie-mutuelle(dot)fr |
| Subject: | Re: BUG #16003: pg_basebackup failed with error : directory "xxxxxxx" exists but is not empty |
| Date: | 2019-09-13 03:42:41 |
| Message-ID: | 20190913034241.GC2285@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vinay Banakar | 2019-09-13 04:13:21 | Re: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg |
| Previous Message | Tom Lane | 2019-09-12 22:28:25 | Re: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg |