Wednesday, June 11, 2008

[ODBC] Re: [GENERAL] what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE

Richard Broersma wrote:
> Server logs below. Notice how an error raised in a connection to the
> proj02u20411 database forces the transaction in the instrumentation
> database to rollback.
> Can anyone explain why connections that as far as PG should conserned
> are unrelated are actually interferring with one another?

I don't see any errors on proj...

> --------------------------------------------------------------------------------
[snip]
> 2008-06-10 15:04:52instrumentation ERROR: syntax error at or near
> "SELECT" at character 16
> 2008-06-10 15:04:52instrumentation STATEMENT: SELECT INVALID SELECT
> STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
> 2008-06-10 15:04:52instrumentation LOG: statement: ROLLBACK

That appears to be a deliberate bad query issued by something (above the
odbc layer?). I think you've got something sending "SELECT INVALID
SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE" as a query to
force a rollback. Why it's not just sending "ROLLBACK" I don't know.

--
Richard Huxton
Archonet Ltd

--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

No comments: