On Tue, Apr 27, 2010 at 4:19 PM, Barry Schatz <barry.sch...@gmail.com> wrote: > I didn't receive a copy of my post from yesterday so I'm having to write > this as if it were a new post rather than a follow-up (keeping same subject > line).
Gmail hides it for you. > FYI: I overcame the problem of pgAgent not reading .pgpass by eliminating > the host address from the arguments, thus: > > DAEMON_ARGS="-l 1 -s /var/log/postgresql/pgagent.log port=6543 > dbname=postgres user=postgres" > > Why did this work? I'm not sure. It would be helpful if someone more > knowledgeable could chime in and correct my discovery that, apparently, > .pgpass works only in a UNIX socket context. Surely that is wrong, but when > I deleted the host address argument pgAgent could use .pgpass via login by > UNIX sockets, with the following line set in pg_hba.conf: From: http://www.postgresql.org/docs/8.4/static/libpq-connect.html "Also, host rather than hostaddr is used to identify the connection in ~/.pgpass (see Section 30.14)." -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
