Re: Mutli-threading and performance of ODBC

> -----Original Message-----
> From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx] 
> Sent: 09 March 2004 16:35
> To: Dave Page
> Cc: Stergios Zissakis; pgsql-odbc@xxxxxxxxxxxxxx; Kostas 
> Lykiardopoulos; Dimitris Pantermalis
> Subject: Re: [ODBC] Mutli-threading and performance of ODBC 
> 
> "Dave Page" <dpage@xxxxxxxxxxxxxxxxxx> writes:
> > I removed KSQO long ago for servers >= 7.3 - for < 7.3 it 
> is a config 
> > option. GEQO is set via a config option - it is not forced on.
> 
> I just looked through the unixODBC 2.2.8 sources, and I can't 
> see anywhere that the behavior for KSQO is made 
> version-dependent.  It seems to be there and default to ON 
> regardless of backend version.

It's not in unixODBC, it's in psqlODBC (and the above should have read
7.1).

From:
http://gborg.postgresql.org/project/psqlodbc/cvs/co.php/psqlodbc/connect
ion.c?r=1.67

        /* KSQO (not applicable to 7.1+ - DJP 21/06/2002) */
        if (ci->drivers.ksqo && PG_VERSION_LT(self, 7.1))
        {
                result = PGAPI_ExecDirect(hstmt, "set ksqo to 'ON'",
SQL_NTS);
                if ((result != SQL_SUCCESS) && (result !=
SQL_SUCCESS_WITH_INFO))
                        status = FALSE;

                mylog("%s: result %d, status %d from set ksqo\n", func,
result, status);

        }

It's in tip as well...

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings