Date: Fri, 25 Mar 2022 13:26:05 +0100
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: michael@paquier.xyz, rjuju123@gmail.com, pgsql-hackers@postgresql.org
Subject: Re: standby recovery fails (tablespace related) (tentative patch and
 discussion)
Message-ID: <202203251226.gtrffvumu2qg@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <202203211843.ufy24c7nzkjr@alvherre.pgsql>
Archived-At: 
 <https://www.postgresql.org/message-id/202203251226.gtrffvumu2qg%40alvherre.pgsql>
Precedence: bulk

On 2022-Mar-21, Alvaro Herrera wrote:

> I had a look at this latest version of the patch, and found some things
> to tweak.  Attached is v21 with three main changes from Kyotaro's v20:

Pushed this, backpatching to 14 and 13.  It would have been good to
backpatch further, but there's an (textually trivial) merge conflict
related to commit e6d8069522c8.  Because that commit conceptually
touches the same area that this bugfix is about, I'm not sure that
backpatching further without a lot more thought is wise -- particularly
so when there's no way to automate the test in branches older than
master.

This is quite annoying, considering that the bug was reported shortly
before 12 went into beta.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"If you have nothing to say, maybe you need just the right tool to help you
not say it."                   (New York Times, about Microsoft PowerPoint)