Postgres Pro
Downloads
Home   >   mailing lists

Re: Reducing some DDL Locks to ShareLock - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Reducing some DDL Locks to ShareLock
Date
Msg-id 22229.1226458626@sss.pgh.pa.us
Whole thread Raw
In response to Re: Reducing some DDL Locks to ShareLock  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Reducing some DDL Locks to ShareLock  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Tree view 
Simon Riggs <simon@2ndQuadrant.com> writes:
> On Mon, 2008-11-10 at 19:15 -0500, Tom Lane wrote:
>> The reason I was thinking about heap_lock_tuple is that it might provide
>> a suitable defense against that case.

> OK. Lock tuple works OK, but its the unlock that I'm worried about. How
> would non-transactional un-lock tuple work?

I was imagining that the heap_inplace_update operation would release the
lock.  Is there some problem with the concept?
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Meaning of transaction pg_locks?
Next
From: Philip Warner
Date:
Subject: Re: Meaning of transaction pg_locks?