From: Richard Huxton <dev@archonet.com>
To: Richard Broersma <richard.broersma@gmail.com>
Cc: PostgreSQL - General ML <pgsql-general@postgresql.org>
Cc: pgsql-odbc@postgresql.org
Subject: Re: what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
Date: Wed, 11 Jun 2008 08:07:28 +0100
Message-ID: <484F79B0.5060401@archonet.com> (raw)
In-Reply-To: <396486430806102106i4915845ag746566c333bdc684@mail.gmail.com>
References: <396486430806102106i4915845ag746566c333bdc684@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: dev@archonet.com, richard.broersma@gmail.com, pgsql-general@postgresql.org, pgsql-odbc@postgresql.org
Subject: Re: what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE
In-Reply-To: <484F79B0.5060401@archonet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox