From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres Account Inherit Question |
Date: | 2011-10-14 17:31:36 |
Message-ID: | 1318613496.2127.69.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2011-10-14 at 18:44 +0200, Julien Rouhaud wrote:
> On Fri, Oct 14, 2011 at 6:38 PM, Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com>wrote:
>
> > I've configured my 'pg_hba.conf' file to look as follows:
> >
> > # "local" is for Unix domain socket connections only
> > local all all md5
> > # IPv4 local connections:
> > host all all 127.0.0.1/32 md5
> > host all all 192.168.0.0/24 md5
> >
> > Now I've reloaded / restarted the PostgreSQL daemon however for some
> > reason when I use the 'postgres' user locally, it never prompts for a
> > password in 'psql'. I've altered the role to NOINHERIT
> >
> > postgres=# ALTER ROLE postgres NOINHERIT;
> > ALTER ROLE
> >
> > Any other role locally requires a password to even list the database
> > using 'psql -l' command except the 'postgres' role. Is this normal
> > behavior or am I missing something here? How can I force the postgres
> > account to be prompted for a password when communicating to the
> > database server locally?
> >
> >
> Hi
> Did you check for a .pgpass file ?
And do you have any other lines before the few ones you give ?
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos Mennens | 2011-10-14 17:43:17 | Re: Postgres Account Inherit Question |
Previous Message | Dario Beraldi | 2011-10-14 17:21:41 | plpython on postgresql 9.1 |