Re: what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE - Mailing list pgsql-general

From Richard Huxton
Subject Re: what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
Date
Msg-id 484F79B0.5060401@archonet.com
Whole thread Raw
In response to what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE  ("Richard Broersma" <richard.broersma@gmail.com>)
Responses Re: what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE  ("Richard Broersma" <richard.broersma@gmail.com>)
List pgsql-general
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

pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: encoding confusion
Next
From: valgog
Date:
Subject: Re: Multithreaded queue in PgSQL