| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_tablespace_location() failure with allow_in_place_tablespaces |
| Date: | 2022-03-04 10:40:51 |
| Message-ID: | YiHss9OAlz57lM1+@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 04, 2022 at 06:04:00PM +0900, Kyotaro Horiguchi wrote:
> And I made a quick hack on do_pg_start_backup. And I found that
> pg_basebackup copies in-place tablespaces under the *current
> directory*, which is not ok at all:(
Yeah, I have noticed that as well while testing such configurations a
couple of hours ago, but I am not sure yet how much we need to care
about that as in-place tablespaces are included in the main data
directory anyway, which would be fine for most test purposes we
usually care about. Perhaps this has an impact on the patch posted on
the thread that wants to improve the guarantees around tablespace
directory structures, but I have not studied this thread much to have
an opinion. And it is Friday.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2022-03-04 10:42:30 | Re: Column Filtering in Logical Replication |
| Previous Message | Thomas Munro | 2022-03-04 10:26:43 | Re: pg_tablespace_location() failure with allow_in_place_tablespaces |