Re: Is FOR UPDATE an optimization fence?

From: Markus Wanner <markus(at)bluegap(dot)ch>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Is FOR UPDATE an optimization fence?
Date: 2009-10-11 17:52:23
Message-ID: 4AD21B57.10507@bluegap.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Tom Lane wrote:
> It's an entirely trivial code change either way. I'm inclined to think
> that we should prevent flattening, on the grounds of least astonishment.

Yeah, I also tend towards making FOR UPDATE an optimization fence
(that's how I understood the non-flattening approach). While it might
change behavior compared to previous versions, it doesn't force people
into writing kludges like OFFSET 0.

BTW: how do other databases deal with this? Anything of relevance in the
SQL standards?

Regards

Markus Wanner

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-10-11 18:00:19 Re: Is FOR UPDATE an optimization fence?
Previous Message Tom Lane 2009-10-11 16:35:07 Is FOR UPDATE an optimization fence?