> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailtogsql-odbc-owner@postgresql.org] On Behalf Of Ludek Finstrle
> Sent: 04 December 2005 21:26
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] Connection error with sslmode (PgSQL 7.3)
>
> Hello,
>
> I register problem with connection to PgSQL 7.3. Error is that
> PgSQL 7.3 doesn't know connection parameter sslmode.
>
> I think about it and try this solution:
> Add SSL mode:
> - none - don't add sslmode to connect string
> - requiressl_try - use requiressl=0 instead of sslmode
> - requiressl_on - use requiressl=1 instead of sslmode
>
> I also change default value from "prefer" to "none". "none" works
> aginist all server versions.

Unless I'm misremebering, this should not be an problem as sslmode is a
libpq thing, so as long as you are using an new enough libpq, everything
should be fine (this is how it works in pgAdmin - we have only the newer
options, yet fully support 7.3+).

This sounds like another reason not to support older libpq's -
especially as the Windows dialogues will suddenly gain options for both
types of ssl options potentially leaving many users confused about which
to use.

> There is a question what about Protocol data source option? Isn't
> it obsolete?

Yes, absolutely. Just haven't got around to removing it yet. There's a
beginners project if ever I saw one - just needs a note in the relevant
places to remind future programmers not to result the old short connect
string option code.

Along similar lines - is manual_result always true with the libpq
driver? If so, there's probably a bunch more code that can go.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

> > I also change default value from "prefer" to "none". "none" works
> > aginist all server versions.
>
> Unless I'm misremebering, this should not be an problem as sslmode is a
> libpq thing, so as long as you are using an new enough libpq, everything
> should be fine (this is how it works in pgAdmin - we have only the newer
> options, yet fully support 7.3+).

Yes. You're absolutely right.

> This sounds like another reason not to support older libpq's -
> especially as the Windows dialogues will suddenly gain options for both
> types of ssl options potentially leaving many users confused about which
> to use.

You're absolutely right.
There is no problem to support only linux version (without Windows
changes). But there is a lot of work not including this.
I agree with you to drop this support.

Luf

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq