I figured this out and it is not a Postgres issue. There was a area of initialization overlooked by the installer on a fresh install of a development system..
I had to add a little extra debug to see that one key job not only was not getting attached to the database, it was not even trying. After seeing that I able to run down the installation flaws. Thanks very much to all for your suggestions on this matter. Regards Dave -----Original Message----- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: Friday, October 23, 2015 12:49 PM To: Day, David Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] strange connection problem. "Day, David" <d...@redcom.com> writes: > I have a development site ( FreeBSD 10.1 and Postgres 9.3 ) where I can > connect to the database via psql or pgadminIII both locally and remotely. > However, all of the local apps ( 3 different ones ) that would connect to it > are failing to connect. Are those apps trying to use TCP connections, or Unix-socket connections? If the latter, it might be a discrepancy in where they expect the socket file to be versus where the postmaster thinks it should be. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
