Date: Wed, 10 Nov 2021 09:14:30 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: michael@paquier.xyz, daniel@yesql.se, guopa@vmware.com,
	tgl@sss.pgh.pa.us, robertmhaas@gmail.com, ibrar.ahmad@gmail.com,
	masao.fujii@oss.nttdata.com, a.lubennikova@postgrespro.ru,
	pasim@vmware.com, thomas.munro@gmail.com,
	horiguchi.kyotaro@lab.ntt.co.jp, pgsql-hackers@postgresql.org
Subject: Re: standby recovery fails (tablespace related) (tentative patch and
 discussion)
Message-ID: <202111101214.buuhq756cbbs@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20211110.171411.1604652159337106356.horikyota.ntt@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202111101214.buuhq756cbbs%40alvherre.pgsql>
Precedence: bulk

On 2021-Nov-10, Kyotaro Horiguchi wrote:

> I bumped into the good-old 100-byte limit of the (v7?) tar format on
> which pg_basebackup is depending. It is unlikely in the real world but
> I think it is quite common in developping environment.  The tablespace
> directory path in my dev environment was 110 chacters-long.  As small
> as 10 bytes but it's quite annoying to chip off that number of bytes
> from the path..

Can you use PostgreSQL::Test::Utils::tempdir_short() for those
tablespaces?

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/