Re: BUG #13188: .pgpass does not work

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: "bzb(dot)dev001(at)gmail(dot)com" <bzb(dot)dev001(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13188: .pgpass does not work
Date: 2015-04-29 20:41:17
Message-ID: CAMkU=1y+F+sg4+UNOPsUc8BfJmiaukSJR8LPAOqoewF7N4Kgag@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Apr 29, 2015 at 11:23 AM, bzb(dot)dev001(at)gmail(dot)com <bzb(dot)dev001(at)gmail(dot)com
> wrote:

>
> I've changed back the owner of .pgpass to the account that I've logged in
> as. This is the account that I'm using to run psql.
> All the spaces in .pgpass is removed.
> Checked that the permission settings of .pgpass is ok.
> restarted the server...
>
> $ sudo service postgresql restart
>
> Unfortunately, it is still not working.
>
> $ psql --host=localhost --port=5432 --username=postgres --no-password
> psql: fe_sendauth: no password supplied
>
>
I wonder if it is even finding the file in the first place.

strace psql --host=localhost --port=5432 --username=postgres
--no-password 2>&1 | fgrep pgpass

This is what I get:

stat("/home/jjanes/.pgpass", {st_mode=S_IFREG|0600, st_size=196, ...}) = 0
open("/home/jjanes/.pgpass", O_RDONLY) = 3

For me it found the file and opened it successfully.

Cheers,

Jeff

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message bzb.dev001@gmail.com 2015-04-29 20:42:57 Re: BUG #13188: .pgpass does not work
Previous Message David G. Johnston 2015-04-29 19:32:26 Re: BUG #13188: .pgpass does not work