Postgres Pro
Downloads
Home   >   mailing lists

Re: Why is lock not released? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Why is lock not released?
Date
Msg-id 22950.1124548093@sss.pgh.pa.us
Whole thread Raw
In response to Re: Why is lock not released?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Tree view 
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Oh, so is RowExclusiveLock not exclusive?  (pokes)  yeah, I guess it
> isn't ...

I'm not sure where we got our lock mode names from, but there are a
number of things that aren't great about the choices.  In particular
"Exclusive" doesn't always mean "exclusive at the table level".
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)
Next
From: Tom Lane
Date:
Subject: Re: Win32 unicode vs ICU