Re: possible deadlock: different lock ordering for heap pages

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>

To: "Nishant, Fnu" <nishantf@amazon.com>

Cc: Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2019-02-04T02:29:08Z

Lists: pgsql-hackers

On Fri, Feb 1, 2019 at 10:50 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Mon, Jan 21, 2019 at 10:39 PM Nishant, Fnu <nishantf@amazon.com> wrote:
> >
> > Thanks Amit for your review.
> >
> > On 1/20/19, 6:55 AM, "Amit Kapila" <amit.kapila16@gmail.com> wrote:
> >     > I think you need to change below code as well....
> >        Assert(buffer2 == InvalidBuffer || buffer1 <= buffer2);
> >
> > Done. Updated the patch.
> >
>
> Attached is an updated patch.  I have edited comments and commit
> message in the patch.  I would like to backpatch this till 9.4 unless
> anyone thinks otherwise.
>

Pushed this patch and backpatched till 9.4.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Commits

Avoid possible deadlock while locking multiple heap pages.
- 0b8bdb3c3ec0 12.0 landed
- fba0a8292997 9.4.21 landed
- 6a2c9c633135 9.5.16 landed
- 073afae81989 9.6.12 landed
- 1ca33fc7b511 10.7 landed
- 904413637f8b 11.2 landed
Try again to make the visibility map crash safe.
- e16954f3d27f 9.2.0 cited