Return to Answer

Notably, you added user_id as 3rd expression to ORDER BY to break ties. That's good. But if you want to keep using Row Constructor Comparison, all 3 expressions must share the same sort direction. All ASCENDING or all DESCENDING. Else it gets more complex and expensive.
Also, add user_id to the SELECT list. It's essential for your pagination.

'2023-03-25 00:11:56+01' is the result of the date_bin() expression. You might add it to the SELECT list for simplicity. (I added it in the fiddle.)

Notably, you added user_id as 3rd expression to ORDER BY to break ties. That's good. But if you want to keep using Row Constructor Comparison, all 3 expressions must share the same sort direction. All ASCENDING or all DESCENDING. (Else it gets more complex and expensive.) See:

• SQL syntax term for 'WHERE (col1, col2) < (val1, val2)'
• How to form a WHERE condition matching multiple ORDER BY items?

Also, add user_id to the SELECT list. It's essential for your pagination.

'2023-03-25 00:11:56+01' is the result of the date_bin() expression. You might add it to the SELECT list for simplicity. (I added it in the fiddle.)

Since your date_bin() expression uses an arbitrary time anchor (and interval?), using an index is sophisticated, but still possible. Work with the lower / upper bounds of possible date_bin() values ...

('2023-03-25 00:11:56+01', 8, 5) being derived from the last row of the first page.
 '2023-03-25 00:11:56+01' is the result of the date_bin() expression. You might add it to the SELECT list for simplicity.

fiddle

fiddle

('2023-03-25 00:11:56+01', 8, 5) being derived from the last row of the first page. 

'2023-03-25 00:11:56+01' is the result of the date_bin() expression. You might add it to the SELECT list for simplicity. (I added it in the fiddle.)

These two timestamptz values are exactly the same:

'2023-03-24 23:11:56+00'
'2023-03-25 00:11:56+01'

The display depends on the timezone setting of your session, the value is the same. Basics:

• Ignoring time zones altogether in Rails and PostgreSQL

('2023-03-25 00:11:56+01', 8, 5) being derived from the last row of the first page.

('2023-03-25 00:11:56+01', 8, 5) being derived from the last row of the first page.
'2023-03-25 00:11:56+01' is the result of the date_bin() expression. You might add it to the SELECT list for simplicity.