Re: postgresql locks the whole table! - Mailing list pgsql-general

From Tom Lane
Subject Re: postgresql locks the whole table!
Date
Msg-id 23392.1070824412@sss.pgh.pa.us
Whole thread Raw
In response to Re: postgresql locks the whole table!  (Mike Mascari <mascarm@mascari.com>)
List pgsql-general
> Greg Stark wrote:
>> This gets the right semantics but without the debugging info of a list of
>> lockers. Other than debugging the only advantage I see to having the list of
>> lockers is for deadlock detection. Is that absolutely mandatory?

No, deadlock detection is not optional.

Mike Mascari <mascarm@mascari.com> writes:
> What happens if a backend is killed and never decrements its reference
> count?

Even if it's not killed, how does it know to decrement the reference
count?  You still need a list of all locked tuples *somewhere*.  Perhaps
a technique like this would allow the list to not be in shared memory,
which is helpful, but it's far from an ideal solution.

            regards, tom lane

pgsql-general by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: postgresql locks the whole table!
Next
From: "Joshua D. Drake"
Date:
Subject: Re: pg_hba.conf change in 7.4