I totally agree with you and the problem is gonna be fixed. I just needed a
temporary solution until the patch goes out.
Thank you,
Ioana
--- On Wed, 3/2/11, Tom Lane wrote:
> From: Tom Lane
> Subject: Re: [GENERAL] select DISTINCT not ordering the returned rows
> To: "Ioan
Ioana Danes, 02.03.2011 21:35:
Hi Everyone,
I would like to ask for your help finding a temporary solution for my problem.
I upgraded postgres from 8.3 to 9.0.3 and I have an issue with the order of the
returned rows.
The database is free to return rows in any order it thinks is most efficie
Ioana Danes writes:
> I upgraded postgres from 8.3 to 9.0.3 and I have an issue with the order of
> the returned rows.
Your application is simply broken if it assumes that DISTINCT results in
ordering the rows. The only thing that guarantees that is an ORDER BY.
You could probably work around
I found it: disabling enable_hashagg
--- On Wed, 3/2/11, Ioana Danes wrote:
> From: Ioana Danes
> Subject: [GENERAL] select DISTINCT not ordering the returned rows
> To: "PostgreSQL General"
> Received: Wednesday, March 2, 2011, 3:35 PM
> Hi Everyone,
>
> I
Hi Everyone,
I would like to ask for your help finding a temporary solution for my problem.
I upgraded postgres from 8.3 to 9.0.3 and I have an issue with the order of the
returned rows.
The following script is a simplification of my real case:
create table tmp_1 (field1 integer, field2 intege