Re: pg_tablespace_location() failure with allow_in_place_tablespaces

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: thomas(dot)munro(at)gmail(dot)com
Cc: michael(at)paquier(dot)xyz, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_tablespace_location() failure with allow_in_place_tablespaces
Date: 2022-03-16 01:34:15
Message-ID: 20220316.103415.804182718531168220.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Tue, 15 Mar 2022 23:16:52 +1300, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote in
> On Tue, Mar 15, 2022 at 10:30 PM Michael Paquier <michael(at)paquier(dot)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.

+1. Desn't the doc need to mention that?

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-03-16 01:39:31 Re: Unhyphenation of crash-recovery
Previous Message Kyotaro Horiguchi 2022-03-16 01:29:47 Re: Add checkpoint and redo LSN to LogCheckpointEnd log message