A long time a special optimizing strategy was devised to improve
performance on the types of queries generated by ODBC clients. Prior to
key set query optimization (KSQO) the postgres optimizer would choke.
In not so recent versions of the backend server the general optimizer
was improved enough to deprecate KSQO. I guess the ODBC driver has
lagged behind. So, at least your version still sends the SET KSQO
command. I believe you can turn this off somewhere in the driver
configuration dialog. In any case it should be harmless.
David
-----Original Message-----
From: kj subbu [mailto:kjsubbu@hotmail.com]
Sent: Friday, January 21, 2005 9:22 AM
To: pgsql-odbc@postgresql.org
Subject: [ODBC] ksqo is not valid option name
Hi Postgres lovers
I have serious problem in postgresql and odbc
.
i have the below things in my server
redhat linux version : 3.0 (EL)
postgres ver :7.3.6
unix odbc version - 2.2.8
when i test the postgresql databse with isql with odbc dsn name is
connectecd perfectly but not is not disconnectd . at the same time i got
the
error : ksqo is not valid option name
I connect the postgresql server with the help of pgadmin is connected
perfectly with unsupported protocol error.
i dont know y the error is coming and this error on ODBC VERISON OR
POSTGRSQL VERSION
can u help me in this issue
Thanks & Regards
Subbiah K J
_________________________________________________________________
Get head hunted by 5000 tech recruiters.
http://www.naukri.com/tieups/tieups.php?othersrcp=534 Post your CV on
Naukri.com.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
