I do not know about Java and jdbc, but had similiar problems with
various Python-Database adapters. Have you double-checked that true
and false are valid options?
you can read
This option determines whether or with what priority an SSL
connection will be negotiated with the server. There are four modes:
disable will attempt only an unencrypted SSL connection; allow will
negotiate, trying first a non-SSL connection, then if that fails,
trying an SSL connection; prefer (the default) will negotiate, trying
first an SSL connection, then if that fails, trying a regular non-SSL
connection; require will try only an SSL connection.
If PostgreSQL is compiled without SSL support, using option
require will cause an error, while options allow and prefer will be
accepted but libpq will not in fact attempt an SSL connection.
so probably you should use "disable" instead of "false", and "require"
or "prefer" instead of true?
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
EuroPython 2008 will take place in Vilnius, Lithuania - Stay tuned!
In response to
pgsql-jdbc by date
|Next:||From: Kris Jurka||Date: 2008-01-28 17:53:50|
|Subject: Re: backpatching 8.2 to deal with batch callable statements|
|Previous:||From: Dave Cramer||Date: 2008-01-28 13:42:07|
|Subject: backpatching 8.2 to deal with batch callable statements|
pgsql-general by date
|Next:||From: Dominique Bessette - Halsema||Date: 2008-01-28 17:30:28|
|Subject: close connection|
|Previous:||From: Harald Fuchs||Date: 2008-01-28 16:53:51|
|Subject: Re: Is news.postgresql.org down?|