Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_tablespace_location() failure with allow_in_place_tablespaces - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: pg_tablespace_location() failure with allow_in_place_tablespaces
Date
Msg-id CA+hUKGKq1A0WB9nFMUUOJyk2TgTUnq0r8Ybk9NiAjfbTpeVc_w@mail.gmail.com
Whole thread Raw
In response to Re: pg_tablespace_location() failure with allow_in_place_tablespaces  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pg_tablespace_location() failure with allow_in_place_tablespaces  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
Tree view 
On Tue, Mar 15, 2022 at 10:30 PM Michael Paquier <michael@paquier.xyz> wrote:
> So, which one of a relative path or an absolute path do you think
> would be better for the user?  My preference tends toward the relative
> path, as we know that all those tablespaces stay in pg_tblspc/ so one
> can make the difference with normal tablespaces more easily.  The
> barrier is thin, though :p

Sounds good to me.

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
Next
From: Amit Kapila
Date:
Subject: Re: Skipping logical replication transactions on subscriber side