From: Tom Lane <tgl@sss.pgh.pa.us>
To: kristone@hotmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18606: syntax error at or near "ROWS"
In-reply-to: <18606-7a775256cbcf4c1e@postgresql.org>
References: <18606-7a775256cbcf4c1e@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 09 Sep 2024 07:40:41 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3145580.1725892966.1@sss.pgh.pa.us>
Date: Mon, 09 Sep 2024 10:42:46 -0400
Message-ID: <3145581.1725892966@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3145581.1725892966%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> 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```

Hmm, what that should look like when it gets to the server,
I imagine, is

  SELECT "Id","Begin","End","Logfile" FROM "ServerSession" ORDER BY "Begin"
  ASC OFFSET $1 ROWS FETCH FIRST $2 ROW ONLY;

which works just fine for me.  I'd suggest peeking into the postmaster
log to see what ODBC is actually sending in the problem cases.  I'm
guessing that pgsql_odbc is doing something bizarre, in which case
you'd be best advised to report this on the pgsql-odbc mailing list.

			regards, tom lane