Re: Postgres offset and limit bug

Поиск
Список
Период
Сортировка
От Ming
Тема Re: Postgres offset and limit bug
Дата
Msg-id SYZP282MB3110F3E7F9C26764A0697BA9E5409@SYZP282MB3110.AUSP282.PROD.OUTLOOK.COM
обсуждение исходный текст
Ответ на Re: Postgres offset and limit bug  (David Rowley <dgrowleyml@gmail.com>)
Список pgsql-bugs
Thanks David~

From: David Rowley <dgrowleyml@gmail.com>
Sent: Thursday, September 8, 2022 7:03:33 PM
To: Ming <ming@cleanstormwater.com.au>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Postgres offset and limit bug
 
On Thu, 8 Sept 2022 at 20:49, Ming <ming@cleanstormwater.com.au> wrote:
> The issue is when I have limit 1 with the offset, the first record id will be 45 (which should be 46) . (Although, it’s ordered by path, the of is actually ordered as well.) But without the limit 1 the results will be correct. And when I plus one to the offset value, the actual offset will increase by 2.
>
> In general, the offset value with 45 is behave as offset 44. But when change the value to other thing, the results will be all good.

That's probably because the path for 45 and 46 are the same and you've
only specified that you want the results ordered by path. If there are
duplicates then the order that duplicates appear in will be
non-deterministic. Maybe you'll want to consider adding
source_template_id to the ORDER BY.

David

В списке pgsql-bugs по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #17610: Use of multiple composite types incompatible with record-typed function parameter
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #17611: SJIS conversion rule about duplicated characters differ from Windows