RE: Wrong FOR UPDATE lock type - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: Wrong FOR UPDATE lock type
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D31C3@sectorbase1.sectorbase.com
Whole thread Raw
In response to Wrong FOR UPDATE lock type  (Jan Wieck <janwieck@yahoo.com>)
Responses Re: Wrong FOR UPDATE lock type
List pgsql-hackers
>     I'm  about  99.666667% sure that the lock type choosen in the
>     FOR UPDATE case (line  511  of  parse_relation.c)  should  be
>     RowExclusiveLock  instead  of  RowShareLock.   Actually I get
>     "Deadlock risk" debug messages when selecting FOR UPDATE  and
>     then really UPDATE.

http://www.postgresql.org/users-lounge/docs/6.5/user/x3116.htm

RowShareLock
Acquired by SELECT FOR UPDATE and LOCK TABLE for IN ROW SHARE MODE
statements. 

Conflicts with ExclusiveLock and AccessExclusiveLock modes. 

Vadim


pgsql-hackers by date:

Previous
From: Dave Smith
Date:
Subject: Re: compiling pg 7.0.3 on sco 5.0.5
Next
From: Thomas Lockhart
Date:
Subject: Re: redundancy and disk i/o