| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | James Coleman <jtc331(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: [DOC] Document concurrent index builds waiting on each other |
| Date: | 2021-01-13 21:14:25 |
| Message-ID: | 20210113211425.GA16487@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-01-13 21:16:04 | Re: [DOC] Document concurrent index builds waiting on each other |
| Previous Message | James Coleman | 2021-01-13 21:08:33 | Re: [DOC] Document concurrent index builds waiting on each other |