From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: James Coleman <jtc331@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: David Johnston <david.g.johnston@gmail.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Cc: Andres Freund <andres@anarazel.de>
Subject: Re: [DOC] Document concurrent index builds waiting on each other
Date: Wed, 13 Jan 2021 18:14:25 -0300
Message-ID: <20210113211425.GA16487@alvherre.pgsql> (raw)
In-Reply-To: <20210113210537.GA15374@alvherre.pgsql>
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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, jtc331@gmail.com, michael@paquier.xyz, david.g.johnston@gmail.com, pgsql-hackers@lists.postgresql.org, andres@anarazel.de
Subject: Re: [DOC] Document concurrent index builds waiting on each other
In-Reply-To: <20210113211425.GA16487@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox