Date: Wed, 13 Jan 2021 18:14:25 -0300
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: James Coleman <jtc331@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
	David Johnston <david.g.johnston@gmail.com>,
	PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>,
	Andres Freund <andres@anarazel.de>
Subject: Re: [DOC] Document concurrent index builds waiting on each other
Message-ID: <20210113211425.GA16487@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20210113210537.GA15374@alvherre.pgsql>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On 2021-Jan-13, Alvaro Herrera wrote:

> I wondered about noting whether only processes in the current database
> are affected, but then I noticed that the current code since commit
> dc7420c2c927 uses a completely different algorithm than what we had with
> GetOldestXmin() and does not consider database boundaries at all.
> This doesn't sound great to me, since a misbehaved database can now
> affect others ...  Maybe I misunderstand that code.

This appears to be false, per ComputeXidHorizons.

-- 
Álvaro Herrera                            39°49'30"S 73°17'W
"Ni aún el genio muy grande llegaría muy lejos
si tuviera que sacarlo todo de su propio interior" (Goethe)