Postgres Pro
Downloads
Home   >   mailing lists

Re: Is FOR UPDATE an optimization fence? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Is FOR UPDATE an optimization fence?
Date
Msg-id 13522.1255284019@sss.pgh.pa.us
Whole thread Raw
In response to Re: Is FOR UPDATE an optimization fence?  (Markus Wanner <markus@bluegap.ch>)
List pgsql-hackers
Tree view 
Markus Wanner <markus@bluegap.ch> writes:
> BTW: how do other databases deal with this? Anything of relevance in the
> SQL standards?

SQL99 treats FOR UPDATE as an attribute of DECLARE CURSOR, so there's
no way for it to appear in a sub-select per spec.  (In general our
approach to FOR UPDATE is only loosely related to what the spec
thinks it does ...)
        regards, tom lane

pgsql-hackers by date:

Previous
From: Markus Wanner
Date:
Subject: Re: Is FOR UPDATE an optimization fence?
Next
From: David Fetter
Date:
Subject: man pages