From: | Sebastian P(dot) Luque <spluque(at)gmail(dot)com> |
---|---|
To: | pgsql-pkg-debian(at)postgresql(dot)org |
Subject: | Re: no password on postgres user and pgagent |
Date: | 2016-05-10 13:07:36 |
Message-ID: | 87d1ouvz6v.fsf@otaria.sebmel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-debian |
On Tue, 10 May 2016 11:08:28 +0200,
Christoph Berg <myon(at)debian(dot)org> wrote:
> Re: Seb 2016-05-10 <87r3daopfm(dot)fsf(at)otaria(dot)sebmel(dot)org>
>> Hello,
>> I'd like to run pgagent with the postgres user, which doesn't have a
>> password. I thought it'd be as simple as setting up an init script
>> as:
>> [ -- Begin <pgagent_start.sh>
>> ---------------------------------------------- ] #! /bin/sh
>> pgagent user=postgres host=localhost dbname=postgres
> The default pg_hba.conf requires md5 passwords for "host=localhost"
> connections.
It's actually set to "peer" in my case (v. 9.5):
[ -- <pg_hba.conf> lines 84 - 85 ------------------------------------------- ]
# Database administrative login by Unix domain socket
local all postgres peer
[ -- End of <pg_hba.conf> lines 84 - 85 ------------------------------------ ]
which is what I want; i.e. get user name from the operating system user
and check that it matches requested database user name. If I understand
right, this means that if I sudo or login as postgres, then that's what
PostgreSQL gets. If postgres has no password and I can login without
one, then the database server shouldn't ask for one. Why does pgagent
expect one?
Thanks,
--
Seb
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2016-05-10 14:20:31 | Re: no password on postgres user and pgagent |
Previous Message | Christoph Berg | 2016-05-10 09:08:28 | Re: no password on postgres user and pgagent |