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

Re: additional message to the bug #7499

From: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
To: Denis Kolesnik <lirex(dot)software(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: additional message to the bug #7499
Date: 2012-08-23 01:57:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On 08/22/2012 08:36 AM, Denis Kolesnik wrote:
> I have now VERY strong argument to consider it is as a bug:
> if there a understandable for SQL language sequence which sorts
> in other fashion when adding "LIMIT".

Underspecified sorts can have unstable results, that's allowed by the 
spec and is a reasonable performance optimisation. If you want stable 
sorts you have to provide a fully defined ordering.

To say this is a bug is a bit like saying that undefined behaviour in C 
is a bug. It isn't, the language and compiler are giving you what 
they're supposed to, just not what you want.

Unstable sorts are a common optimisation

and a very useful one. Not allowing Pg to use unstable sorts, or use 
different sorts for different query plans, would slow correct queries 
down to make an incorrect query like yours run how you expect.

Craig Ringer

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2012-08-23 02:24:11
Subject: Re: BUG #4958: Stats collector hung on WaitForMultipleObjectsEx while attempting to recv a datagram
Previous:From: Tom LaneDate: 2012-08-23 01:26:27
Subject: Re: bug #7499 additional comments

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