Re: Issue in GIN fast-insert: XLogBeginInsert + Read/LockBuffer ordering

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zhang Mingli <zmlpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Subject: Re: Issue in GIN fast-insert: XLogBeginInsert + Read/LockBuffer ordering
Date: 2022-10-26 00:43:53
Message-ID: Y1iCyexF653fPxY7@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 25, 2022 at 09:37:08AM +0200, Alvaro Herrera wrote:
> Okay, so if we follow this argument, then the logical conclusion is that
> this *should* be backpatched, after all.

After sleeping on it and looking at all the stable branches involved,
backpatched down to v10.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2022-10-26 01:38:22 Re: Allow WindowFuncs prosupport function to use more optimal WindowClause options
Previous Message Thomas Munro 2022-10-25 23:28:53 Re: [PATCH] Fix build with LLVM 15 or above