Re: 8.4b1: Query returning results in different order to 8.3

From: Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Ian Barwick <barwick(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 8.4b1: Query returning results in different order to 8.3
Date: 2009-04-18 22:19:59
Message-ID: 6313450A-7C84-42CD-83E2-FDF074AAC74E@pointblue.com.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 18 Apr 2009, at 22:22, Tom Lane wrote:
>
> This is mentioned in the release notes, but I suppose we'd better
> promote it to the "observe the following incompatibilities" list...
>

This is a really funny one, because people naturally expect UNION
[ALL] to stay in the same order. Unlike the table, order here cannot
change by inserts/updates, etc.
I am sure many, even well experienced will stumble upon that one.

Me is guessing, that UNION [ALL] performance just had to be improved
for CTEs ? Or was it something completely separate.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-04-18 22:33:49 Re: 8.4b1: Query returning results in different order to 8.3
Previous Message Tom Lane 2009-04-18 21:41:21 Re: [GENERAL] Performance of full outer join in 8.3