From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Igor Neyman <ineyman(at)perceptron(dot)com> |
Cc: | "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: default ordering of query result - are they always guarantee |
Date: | 2010-05-20 14:15:56 |
Message-ID: | AANLkTimKf0ODCSBxYIIF4AWxeI4l9y1RN3Qf6uG-Of6M@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, May 20, 2010 at 8:11 AM, Igor Neyman <ineyman(at)perceptron(dot)com> wrote:
>
>
>> -----Original Message-----
>> From: Scott Marlowe [mailto:scott(dot)marlowe(at)gmail(dot)com]
>> Sent: Wednesday, May 19, 2010 4:15 AM
>> To: A. Kretschmer
>> Cc: pgsql-general(at)postgresql(dot)org
>> Subject: Re: default ordering of query result - are they
>> always guarantee
>>
>> ...................................
>> ...................................
>>
>> Just for reference I once had three separate oracle dbas
>> saying my pg server was broken because group by came out in
>> random order (due to hash aggregates).
>>
>
> Must be not very good dbas :)
> Oracle never guaranteed that "GROUP BY" returns sorted results.
> It's just happened that in earlier Oracle versions they were sorted due
> to algorithm being used for GROUP BY.
> But again, Oracle never guaranteed it.
Actually they were pretty good, but this was several years ago, and
they only had experience with Oracle 8, 9 was all shiny and new to
them. And they had the typical "If Oracle does X, it must be the way
things should be everywhere" Oracle DBA attitude.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-05-20 14:16:16 | Re: setting contrib lo visible to all schemas |
Previous Message | Igor Neyman | 2010-05-20 14:11:28 | Re: default ordering of query result - are they always guarantee |