Re: BUG #4779: LIMIT/OFFSET behavior change (possibly related to Top-n) - Mailing list pgsql-bugs

From Thomas S. Chin
Subject Re: BUG #4779: LIMIT/OFFSET behavior change (possibly related to Top-n)
Date
Msg-id 49F1CE12.5010000@genx.net
Whole thread Raw
In response to Re: BUG #4779: LIMIT/OFFSET behavior change (possibly related to Top-n)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Ah, okay, found the documentation mentioning this (LIMIT).  I was
looking in the wrong place (ORDER BY clause).

Thanks again for the help.

Tom Lane wrote:
> "Thomas S. Chin" <thom@genx.net> writes:
>> I noticed that the behavior of queries that involve LIMIT/OFFSET no longer
>> return results consistent with the ordering of the same query without
>> LIMIT/OFFSET:
>
> No, this is not considered a bug; no such behavior has ever been
> promised.  Read the fine manual.
>
> (Your actual problem is that the sort ordering is underspecified, which
> means you'll get varying results anyway.)
>
>             regards, tom lane

pgsql-bugs by date:

Previous
From: Christine Penner
Date:
Subject: Re: BUG #4771: Postgres wont start
Next
From: "Ted Holzman"
Date:
Subject: BUG #4780: Aggregate functions are unaware of LIMIT clauses in SELECTs