Re: pgAgent and pgpass

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Barry Schatz <barry(dot)schatz(at)gmail(dot)com>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: pgAgent and pgpass
Date: 2010-04-27 15:32:27
Message-ID: l2g937d27e11004270832g7bd5ebu5a6ffcac2760a80f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On Tue, Apr 27, 2010 at 4:19 PM, Barry Schatz <barry(dot)schatz(at)gmail(dot)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

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Hervé Hénoch 2010-04-29 05:55:15 pgadmin3 1.10.2 under Lenny
Previous Message Barry Schatz 2010-04-27 15:19:31 pgAgent and pgpass