On Saturday, November 19, 2011 2:44:04 pm Phoenix Kiula wrote: > On Sun, Nov 20, 2011 at 3:35 AM, Adrian Klaver <adrian.klaver@xxxxxxxxx> wrote: > > Well in the .ini file you posted there is no [databases] section. From > > what I read lack of one would explain the problem you are seeing. > > Yes. Because that's private to post on a public mailing list like this. > > Here's my INI file below, with the private DB name etc sanitizes -- > and trust me, all info related to password and ports is absolutely > correctly entered. Both pgbouncer and postgresql are live and running. > > Just that pg_connect() function in PHP is not working if I point is to > pgbouncer's port instead of the direct postgresql port. I would first work on establishing that psql works. >From a previous post: " Also, this does NOT work: psql snipurl -E "snipurl_snipurl" -p 6543 Shows me this error: psql: ERROR: no working server connection How come? The pgbouncer is on! " Not sure what platform you are on but: http://www.postgresql.org/docs/9.0/interactive/app-psql.html "Not all of these options are required; there are useful defaults. If you omit the host name, psql will connect via a Unix-domain socket to a server on the local host, or via TCP/IP to localhost on machines that don't have Unix-domain sockets" You have pgbouncer listening on 127.0.0.1. In your psql connection string you are not specifying a host, so if you are on a Unix platform it is trying to connect to a socket which would account for the error. I found when working with new software explicit is better than implicit. Eliminate possible sources of error by fully qualifying everything. -- Adrian Klaver adrian.klaver@xxxxxxxxx -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
