From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marko Tiikkaja <marko(at)joh(dot)to> |
Cc: | vetri_2020(at)yahoo(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #10207: Simple select query returns duplicate row - Critical issue |
Date: | 2014-05-03 17:31:50 |
Message-ID: | 29145.1399138310@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Marko Tiikkaja <marko(at)joh(dot)to> writes:
> On 5/3/14, 1:04 PM, vetri_2020(at)yahoo(dot)com wrote:
>> I'd encountered an issue in select query when using order by and limit.
>>
>> When I sort by a column which have same values for some data,then the row
>> that appears in first page also appears in next page.
> This is not a bug. The sort order of identical values is undefined
> unless disambiguated by adding more sort expressions.
Somebody else asked this identical question just a couple days ago:
It's not random in the sense of having any indeterminate behavior,
but the output ordering of equal-keyed elements *can* change depending
on the LIMIT value.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G Johnston | 2014-05-03 22:32:43 | Re: BUG #10207: Simple select query returns duplicate row - Critical issue |
Previous Message | Marko Tiikkaja | 2014-05-03 17:22:28 | Re: BUG #10207: Simple select query returns duplicate row - Critical issue |