Thread: BUG #2269: cannot connect to postgres database on Linux

BUG #2269: cannot connect to postgres database on Linux

From
"Ken"
Date:
The following bug has been logged online:

Bug reference:      2269
Logged by:          Ken
Email address:      kgerdes@opushealthcare.com
PostgreSQL version: 7.3.4
Operating system:   Linux
Description:        cannot connect to postgres database on Linux
Details:

I just downloaded pgAdminIII for Windows to use to connect to our postgres
databases on Linux.  The problem I have is that when I enter the password, I
get this error:

Error has occurred
Error connecting to the server: missing "=" after """ in connection info
string.

The passwords to our databases contain the characters ; and ', which is what
is probably causing this problem.  Can this be resolved or is there a temp
fix to get around this problem?

Re: BUG #2269: cannot connect to postgres database on Linux

From
"Dave Page"
Date:
=20

> -----Original Message-----
> From: pgsql-bugs-owner@postgresql.org=20
> [mailto:pgsql-bugs-owner@postgresql.org] On Behalf Of Ken
> Sent: 16 February 2006 17:47
> To: pgsql-bugs@postgresql.org
> Subject: [BUGS] BUG #2269: cannot connect to postgres=20
> database on Linux
>=20
>=20
> The following bug has been logged online:
>=20
> Bug reference:      2269
> Logged by:          Ken
> Email address:      kgerdes@opushealthcare.com
> PostgreSQL version: 7.3.4
> Operating system:   Linux
> Description:        cannot connect to postgres database on Linux
> Details:=20
>=20
> I just downloaded pgAdminIII for Windows to use to connect to=20
> our postgres
> databases on Linux.  The problem I have is that when I enter=20
> the password, I
> get this error:
>=20
> Error has occurred
> Error connecting to the server: missing "=3D" after """ in=20
> connection info
> string.
>=20
> The passwords to our databases contain the characters ; and=20
> ', which is what
> is probably causing this problem.  Can this be resolved or is=20
> there a temp
> fix to get around this problem?

I've committed fixes to pgAdmin which was incorrectly escaping single
quotes with another single quote (in the same way as we do for string
values in SQL).=20

Thanks for the report.

Regards, Dave.