Re: cvs postgresql current lacks 'ksqo' ? odbc/pgadmin does not work - Mailing list pgsql-general

From Tom Lane
Subject Re: cvs postgresql current lacks 'ksqo' ? odbc/pgadmin does not work
Date
Msg-id 9196.1029343325@sss.pgh.pa.us
Whole thread Raw
In response to cvs postgresql current lacks 'ksqo' ? odbc/pgadmin does not work  (Tino Wildenhain <tino@wildenhain.de>)
Responses Re: cvs postgresql current lacks 'ksqo' ? odbc/pgadmin does  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-general
Tino Wildenhain <tino@wildenhain.de> writes:
> Since I like to try some things out I would be happy with
> a quick dirty patch, but neither the pgodbc source compiles
> nor do I find the relevant parts to the option setting in
> the postgres-sources so I could at least get it to a
> "dummy-accept"

Can't help you with pgodbc, but if you want "set ksqo" to be
accepted, add a dummy variable in src/backend/utils/misc/guc.c
(look at the entry for geqo for a model).

> Btw, what happend to the ksqo anyways?

It's been dead for several releases and showed no sign of ever getting
fixed, so Bruce decided to take it out.

Breaking older odbc drivers might be a sufficient reason to leave a
dummy SET variable in there awhile longer, though.  Not sure.  The
schema changes in 7.3 might mean that using an old driver would be a
bad idea anyway.

            regards, tom lane

pgsql-general by date:

Previous
From: dbdweeb
Date:
Subject: Evaluating PostgreSQL for Production Web App
Next
From: Greg Copeland
Date:
Subject: SF moving to DB2...