Re: bug #7499 additional comments - Mailing list pgsql-bugs

From Tom Lane
Subject Re: bug #7499 additional comments
Date
Msg-id 27428.1345685187@sss.pgh.pa.us
Whole thread Raw
In response to bug #7499 additional comments  (Denis Kolesnik <lirex.software@gmail.com>)
List pgsql-bugs
Denis Kolesnik <lirex.software@gmail.com> writes:
> You would sugguest, that one should read documentation.

Indeed.

> in the (where with ... replaced a directory in which the PostgreSQL installed)
> ...PostgreSQL\9.1\doc\postgresql\html\queries-limit.html

> "...When using LIMIT, it is important to use an ORDER BY clause that
> constrains the result rows into a unique order. .."

> here asked to use "ORDER BY" which is done in every query above.

What you are stubbornly refusing to grasp is that your ORDER BY is not
sufficient to ensure a unique order.  The above-quoted sentence does not
promise that any old ORDER BY will do.  If you simply ORDER BY a
non-unique column, the query's output ordering is only constrained up to
the point that rows with the same ordering value will be adjacent.
If you want more than that, you need to add additional columns to the
ORDER BY to resolve cases where that column is equal.

As long as you haven't done that, you are wrong, and you are wasting
both your time and ours arguing about it.  You've wasted quite enough
of my time already; don't expect to see any further responses on this
subject.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Denis Kolesnik
Date:
Subject: bug #7499 additional comments
Next
From: Tom Lane
Date:
Subject: Re: BUG #4958: Stats collector hung on WaitForMultipleObjectsEx while attempting to recv a datagram