Re: Postgres offset and limit bug - Mailing list pgsql-bugs

From Ming
Subject Re: Postgres offset and limit bug
Date
Msg-id SYZP282MB3110CF86BB76ABA3983CC38FE5409@SYZP282MB3110.AUSP282.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Postgres offset and limit bug  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-bugs
Hello David, 

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. 

Regards, 
Ming 

From: David Rowley <dgrowleyml@gmail.com>
Sent: Thursday, September 8, 2022 6:36:04 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 19:20, Ming <ming@cleanstormwater.com.au> wrote:
> We recently found a strange behavior on Postgres SQL. The offset function will not acting properly when having limit in the query. I want to confirm that it's an existing bug or it's my syntax is wrong.

Nothing looks wrong from here. Can you describe what behaviour you're expecting?

David

pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: Postgres offset and limit bug
Next
From: David Rowley
Date:
Subject: Re: Postgres offset and limit bug