"The search condition of the command (the WHERE clause) is re-evaluated to see if the updated version of the row still matches the search condition. If so, the second updater proceeds with its operation, starting from the updated version of the row."

Hey....that's neat. All this time, I've done an unncessary extra select to see if the value has changed because of competing processes trying to work on same row....

Once again...kudos to lists like this one and of course, RTFM.

Jeff



Tom Lane wrote:

Jeff Amiel <[EMAIL PROTECTED]> writes:


"the docs say that in case of locked rows the where clause is reevaluated: "





Is this true?
Which docs are you refering to (I could find no mention in the postgres docs).....



Second paragraph in http://developer.postgresql.org/docs/postgres/transaction-iso.html#XACT-READ-COMMITTED

                        regards, tom lane






--
Jeff Amiel
Systems/Development Manager
iStream Imaging, an iTeam Company
[EMAIL PROTECTED]
(262) 796-0925 x1011



---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
     subscribe-nomail command to [EMAIL PROTECTED] so that your
     message can get through to the mailing list cleanly

Reply via email to