Wrong FOR UPDATE lock type - Mailing list pgsql-hackers

From Jan Wieck
Subject Wrong FOR UPDATE lock type
Date
Msg-id 200012041252.HAA17027@jupiter.jw.home
Whole thread Raw
Responses Re: Wrong FOR UPDATE lock type  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,
   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
selectingFOR UPDATE  and   then really UPDATE.
 
   Should I change it?


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #




pgsql-hackers by date:

Previous
From:
Date:
Subject: EAN13 for postgresql
Next
From: Fabio Nanni
Date:
Subject: triggers and actions tree