From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | kristone(at)hotmail(dot)com |
Subject: | BUG #18606: syntax error at or near "ROWS" |
Date: | 2024-09-09 07:40:41 |
Message-ID: | 18606-7a775256cbcf4c1e@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 18606
Logged by: Kristian Ivarsson
Email address: kristone(at)hotmail(dot)com
PostgreSQL version: 16.4
Operating system: Microsoft Windows 10 Enterprise Version 10.0.19044
Description:
Using installed version16.4 (even though SQL_DBMS_NAME says version 16.0.4)
with driver PSQLODBC35W.DLL version 13.02.0000)
This error occurs only with some statements when using binding parameters
through ODBC
This statement is an example of when the error occurs
```SELECT "Id","Begin","End","Logfile" FROM "ServerSession" ORDER BY "Begin"
ASC OFFSET ? ROWS FETCH FIRST ? ROW ONLY```
but some more complex SQL statements (with ```OFFSET ? ROWS FETCH FIRST ?
ROW ONLY```) works just fine
Having fixed values (e.g. ```OFFSET 100 ROWS FETCH FIRST 10 ROW ONLY```)
works just fine
I still haven't figured out the pattern what the differences really are that
make some statements to work and some not to work (I haved dugged into the
open source code at all (yet))
/ Kristian
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2024-09-09 08:57:56 | Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows |
Previous Message | Michael Paquier | 2024-09-09 07:21:19 | Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows |