Simon Riggs <[EMAIL PROTECTED]> 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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
