From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "bzb(dot)dev001(at)gmail(dot)com" <bzb(dot)dev001(at)gmail(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #13188: .pgpass does not work |
Date: | 2015-04-29 15:50:05 |
Message-ID: | CAKFQuwZKFJ=Rno6_OGLYDi=6kQOnWoGXBX_9j2S0tqOMLXzmEw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Apr 29, 2015 at 8:09 AM, bzb(dot)dev001(at)gmail(dot)com <bzb(dot)dev001(at)gmail(dot)com>
wrote:
> On 2015-04-29 01:06 AM, David G. Johnston wrote:
>
> On Tuesday, April 28, 2015, <bzb(dot)dev001(at)gmail(dot)com> wrote:
>
>>
>> file: ~/.pgpass
>> ---------------
>> #hostname : port : database : username : password
>> * : 5432 : * : postgres : somepassword
>>
>>
>> When I exec psql without specifying the password, I cannot login...
>>
>> $ psql --host=localhost --port=5432 --username=postgres --no-password
>> psql: fe_sendauth: no password supplied
>>
>>
>>
> I would also remove the padding white space. The syntax is documented
> without and while the documentation is non-specific I've personally always
> avoided it and have never had a problem.
>
>
And excessive whitespace?
Have you confirmed that you are able to connect by supplying the password
manually?
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | bzb.dev001@gmail.com | 2015-04-29 15:57:19 | Re: BUG #13188: .pgpass does not work |
Previous Message | bzb.dev001@gmail.com | 2015-04-29 15:09:28 | Re: BUG #13188: .pgpass does not work |