Skip site navigation (1) Skip section navigation (2)

Re: out-of-order caution

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>
Cc: "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: out-of-order caution
Date: 2011-10-28 14:44:15
Message-ID: 4EAA796F020000250004280A@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
> On Thu, Oct 27, 2011 at 4:41 PM, Kevin Grittner
> <Kevin(dot)Grittner(at)wicourts(dot)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.
 
OK, doc patch attached.
 
-Kevin


Attachment: select-order-by-caution.patch
Description: text/plain (1.5 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-10-28 15:01:20
Subject: Re: Documentation mistake
Previous:From: Vik ReykjaDate: 2011-10-28 14:22:46
Subject: Documentation mistake

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group