MIME-Version: 1.0
References: <E1iXAuR-0001k9-Cn@gemulon.postgresql.org>
 <21620.1581098806@sss.pgh.pa.us>
 <31240.1581267932@sss.pgh.pa.us>
In-Reply-To: <31240.1581267932@sss.pgh.pa.us>
From: Alexander Korotkov <a.korotkov@postgrespro.ru>
Date: Mon, 10 Feb 2020 19:03:48 +0300
Message-ID: 
 <CAPpHfdvs9DXPG75PJ_k7TiHsqQEJzZJi7H0temAX3pUp80wh9w@mail.gmail.com>
Subject: Re: pgsql: Fix page modification outside of critical section in GIN
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alexander Korotkov <akorotkov@postgresql.org>,
	pgsql-committers <pgsql-committers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Sun, Feb 9, 2020 at 8:05 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I wrote:
> > Alexander Korotkov <akorotkov@postgresql.org> writes:
> >> Fix page modification outside of critical section in GIN
>
> > I happened to notice, while reviewing stuff for the release notes,
> > that this patch does not do what the commit message says.  The
> > previous code modified the pd_prune_xid of the "dBuffer" page,
> > but now it's modifying the pd_prune_xid of the "lBuffer" page.
> > Is that actually correct?
>
> Since we're rapidly approaching the wrap deadline for this week's
> releases, I took it upon myself to review this code more carefully,
> and concluded that indeed it isn't correct.  I pushed a fix that
> moves the GinPageSetDeleteXid call again.

Sorry for delayed response.  Yes, my fix for oversight contain
oversight itself.  I confirm the fix you've committed is correct.
Thank you!

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company