Re: pg_tablespace_location() failure with allow_in_place_tablespaces

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_tablespace_location() failure with allow_in_place_tablespaces
Date: 2022-03-15 01:44:03
Message-ID: CA+hUKGLOte+-xjFJhJ7+TEpw7x=7irvRweJjBOug4ke7UkZ06g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 15, 2022 at 2:33 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> As for the complaint about pg_tablespace_location() failing, would it
> be better to return an empty string? That's what was passed in as
> LOCATION. Something like the attached.

(Hrrmm, the contract for pgwin32_is_junction() is a little weird:
false means "success, but no" and also "failure, you should check
errno". But we never do.)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-03-15 01:50:53 Re: pg_tablespace_location() failure with allow_in_place_tablespaces
Previous Message kuroda.hayato@fujitsu.com 2022-03-15 01:39:49 RE: Handle infinite recursion in logical replication setup