Re: pg_tablespace_location() failure with allow_in_place_tablespaces

Alvaro Herrera <alvherre@alvh.no-ip.org>

From: Alvaro Herrera <alvherre@alvh.no-ip.org>

To: Thomas Munro <thomas.munro@gmail.com>

Cc: Michael Paquier <michael@paquier.xyz>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2022-07-22T06:49:31Z

Lists: pgsql-hackers

On 2022-Jul-22, Thomas Munro wrote:

> Thanks.  Pushed.  Also CC'ing Alvaro who expressed an interest in this
> problem[1].

> [1] https://postgr.es/m/20220721111751.x7hod2xgrd76xr5c%40alvherre.pgsql

Yay!  Thanks.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Los dioses no protegen a los insensatos.  Éstos reciben protección de
otros insensatos mejor dotados" (Luis Wu, Mundo Anillo)

Commits

Remove unnecessary Windows-specific basebackup code.
- 202b56ba91cb 15.0 landed
- 5344723755bd 16.0 landed
Fix get_dirent_type() for Windows junction points.
- fee0165fc1cf 14.5 landed
- 6d306ab73168 15.0 landed
- 9d3444dcce4d 16.0 landed
doc: Remove mention to in-place tablespaces for pg_tablespace_location()
- 7a7cd84893e0 15.0 landed
Fix pg_tablespace_location() with in-place tablespaces
- f6f0db4d6240 15.0 landed
Fix pg_basebackup with in-place tablespaces.
- c6f2f01611d4 15.0 landed