Re: pg_tablespace_location() failure with allow_in_place_tablespaces

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

At Thu, 17 Mar 2022 16:39:52 +0900, Michael Paquier <michael(at)paquier(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2022-03-17 08:23:55 Re: pg_walinspect - a new extension to get raw WAL data and WAL stats
Previous Message Kyotaro Horiguchi 2022-03-17 08:05:10 Re: Out-of-tree certificate interferes ssltest