Re: BUG #4884: Misleading error message

From: "Chu, William" <wchu(at)FACorelogic(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #4884: Misleading error message
Date: 2009-06-25 23:28:30
Message-ID: 041EAB7263A00547B7A8251487859F490A270911@CITGSNA01SXCH02.ana.firstamdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom,

What's odd is after the DBA added the proper IP address entries to the
pg_hba.conf I was able to connect properly.

Regards,
Wil

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, June 25, 2009 4:27 PM
To: Chu, William
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #4884: Misleading error message

"William Chu" <wchu(at)facorelogic(dot)com> writes:
> The following error message occurs when the IP address is not present
in the
> pg_hba.conf. The error message is misleading and should actually say
> something to the effect, "Connection refused due to lack of access
> permission".

> java.io.IOException: An SQL exception occurred: ERROR: could not load
> library "/usr/local/pgsql/lib/libpostgis.so.0.9": libgeos.so.2: cannot
open
> shared object file: No such file or directory

Huh? That error message can't possibly have anything to do with the
contents of pg_hba.conf. What it looks like to me is a broken PostGIS
installation, ie, libpostgis present but libgeos missing. If you're
seeing it at connect time, perhaps you have postgis set up as a
preloaded library?

regards, tom lane
******************************************************************************************
This message may contain confidential or proprietary information intended only for the use of the
addressee(s) named above or may contain information that is legally privileged. If you are
not the intended addressee, or the person responsible for delivering it to the intended addressee,
you are hereby notified that reading, disseminating, distributing or copying this message is strictly
prohibited. If you have received this message by mistake, please immediately notify us by
replying to the message and delete the original message and any copies immediately thereafter.

Thank you.
******************************************************************************************
FACLD

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Simon Riggs 2009-06-25 23:30:29 Re: BUG #4879: bgwriter fails to fsync the file in recovery mode
Previous Message Tom Lane 2009-06-25 23:26:33 Re: BUG #4884: Misleading error message