Thread: 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
inthe 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

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’sordered by path, the of is actually ordered as well.) But without the limit 1 the results will be correct. And when
Iplus 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
willbe 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