On Thu, Oct 27, 2011 at 4:41 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> On the docs page for the SELECT statement, there is a caution which
> starts with:
>
> | It is possible for a SELECT command using ORDER BY and FOR
> | UPDATE/SHARE to return rows out of order. This is because ORDER BY
> | is applied first.
>
> Is this risk limited to queries running in READ COMMITTED
> transactions? If so, I think that should be mentioned in the
> caution.
I think it should say that if this occurs with SERIALIZED transactions
it will result in a serialisation error.
Just to say there is no effect in serializable mode wouldn't be helpful.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services