Re: Deadlock possibility in _bt_check_unique?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gokulakannan Somasundaram <gokul007(at)gmail(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Deadlock possibility in _bt_check_unique?
Date: 2010-03-23 18:40:37
Message-ID: 4293.1269369637@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gokulakannan Somasundaram <gokul007(at)gmail(dot)com> writes:
> Consider Time instances T1, T2, T3, T4

> T1 : session 1 holds the write lock on page p1 and completes the unique
> check on p1, p2 and p3.

> T2 : session 1 releases the lock on p1 (its waiting to acquire a ex lock on
> p2)

That's not what we do. See _bt_findinsertloc.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-03-23 18:43:58 Re: Proposal: access control jails (and introduction as aspiring GSoC student)
Previous Message Gurjeet Singh 2010-03-23 18:09:34 Re: Repeating Append operation