Re: pg_tablespace_location() failure with allow_in_place_tablespaces

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

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2022-03-17 07:45:35 Re: Unhyphenation of crash-recovery
Previous Message Andres Freund 2022-03-17 07:36:52 Re: shared-memory based stats collector - v66