Re: BUG #13188: .pgpass does not work - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #13188: .pgpass does not work
Date
Msg-id CAKFQuwZ7DC=zC0CxHqUAnf47iJXcSceNJpH4j2Xhgndm=unYxA@mail.gmail.com
Whole thread Raw
In response to BUG #13188: .pgpass does not work  (bzb.dev001@gmail.com)
Responses Re: BUG #13188: .pgpass does not work  ("bzb.dev001@gmail.com" <bzb.dev001@gmail.com>)
List pgsql-bugs
On Wed, Apr 29, 2015 at 8:09 AM, bzb.dev001@gmail.com <bzb.dev001@gmail.com=
>
wrote:
 I have even changed the ownership of the file to postgres:postgres since
I'm logged on as another user and .pgpass is located in this user's home
directory. Yet it still does not work.
>
>
> $ ls -l .pgpass
> -rw------- 1 postgres postgres 79 Apr 29 10:24 .pgpass
>

=E2=80=8BSorry, I missed this the first time reading.  This is your problem=
.  The
"postgres" Linux user and the "postgres" PostgreSQL user are not related to
each other - particularly when using md5 authentication.  The permissions
on the .pgpass file must be of the user executing "psql" - which you've
indicated is not "postgres".

So, likely your first attempt failed because you had whitespace.  You
changed the permissions and now have two problems.  You then fix the
whitespace and are back to a single problem.  Change the permissions back
and it should now work.

David J.

=E2=80=8B

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #13188: .pgpass does not work
Next
From: Jeff Janes
Date:
Subject: Re: Re: BUG #12990: Missing pg_multixact/members files (appears to have wrapped, then truncated)