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

From Kyotaro Horiguchi
Subject Re: pg_tablespace_location() failure with allow_in_place_tablespaces
Date
Msg-id 20220317.170737.1367754632662165718.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: pg_tablespace_location() failure with allow_in_place_tablespaces  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
At Thu, 17 Mar 2022 16:39:52 +0900, Michael Paquier <michael@paquier.xyz> wrote in 
> On Thu, Mar 17, 2022 at 07:55:30PM +1300, Thomas Munro wrote:
> > I don't really want to spill details of this developer-only stuff onto
> > more manual sections...  It's not really helping users if we confuse
> > them with irrelevant details of a feature they shouldn't be using, is
> > it?  And the existing treatment "Returns the file system path that
> > this tablespace is located in" is not invalidated by this special
> > case, so maybe we shouldn't mention it?
> 
> Right, I see your point.  The existing description is not wrong
> either.  Fine by me to just drop all that.

+1.  Sorry for my otiose comment..

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Out-of-tree certificate interferes ssltest
Next
From: Bharath Rupireddy
Date:
Subject: Re: pg_walinspect - a new extension to get raw WAL data and WAL stats