Re: possible deadlock: different lock ordering for heap pages

From: "Nishant, Fnu" <nishantf(at)amazon(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: possible deadlock: different lock ordering for heap pages
Date: 2019-01-21 17:09:38
Message-ID: 8935951A-0F4D-42D5-AC9A-1EF5A4B907F2@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks Amit for your review.

On 1/20/19, 6:55 AM, "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com> wrote:
> I think you need to change below code as well....
Assert(buffer2 == InvalidBuffer || buffer1 <= buffer2);

Done. Updated the patch.

Will wait for Robert comments.

Thanks
-Nishant

Attachment Content-Type Size
lock-order.patch application/octet-stream 842 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-01-21 17:28:08 Re: "ALTER TRIGGER .. RENAME TO" broken with the "Remove WITH OIDS" commit.
Previous Message Tom Lane 2019-01-21 17:09:30 Re: Thread-unsafe coding in ecpg