Re: Fundamental change of locking behavior in 7.1 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Fundamental change of locking behavior in 7.1
Date
Msg-id 14745.974509986@sss.pgh.pa.us
Whole thread Raw
In response to RE: Fundamental change of locking behavior in 7.1  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
List pgsql-hackers
"Hiroshi Inoue" <Inoue@tpf.co.jp> writes:
> In PostgreSQL,'lock table' acquires a AccessExclusiveLock by default.
> IMHO ExclusiveLock is sufficient for ordinary purpose.

People who want that kind of lock can get it with LOCK TABLE IN
EXCLUSIVE MODE.  I do not think it's a good idea to change the
default kind of lock acquired by a plain LOCK TABLE, if that's
what you're suggesting ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Varchar standard compliance
Next
From: Bruce Momjian
Date:
Subject: Re: location of Unix socket