Re: Postgres offset and limit bug

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

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: David Rowley <dgrowleyml(at)gmail(dot)com>
Sent: Thursday, September 8, 2022 6:36:04 PM
To: Ming <ming(at)cleanstormwater(dot)com(dot)au>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgres offset and limit bug

On Thu, 8 Sept 2022 at 19:20, Ming <ming(at)cleanstormwater(dot)com(dot)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