Re: BUG #13976: how to declare an empty password on .pgpass file

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: chiya2(at)gmail(dot)com
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13976: how to declare an empty password on .pgpass file
Date: 2016-02-22 22:05:45
Message-ID: CAKFQuwYcbdru3sBfHuXPxLfwZc4qs_PV2DWXoikg2xuepLMzew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Feb 22, 2016 at 2:50 AM, <chiya2(at)gmail(dot)com> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 13976
> Logged by: venkata seshadri
> Email address: chiya2(at)gmail(dot)com
> PostgreSQL version: 9.3.2
> Operating system: ubuntu linux
> Description:
>
> Hi
> how to declare an empty password in the .pgpass file.
> *:5432:xxxx:user1:*
>
> i tried with the above option with '*' which accepts any parameter. but
> still un luck. Please help me out on this
>

​Running extremely old 9.3.2 and using "blank" for passwords...hmmmm

Anyway, did you try just leaving it "blank"

*:5432:xxxx:user:

​And, "any value" makes little sense when it comes to passwords in .pgpass
- the password is the exact value it needs to provide to the server so what
specific value would it choose if you could tell it to pick "any" value?
The other pieces are inputs and so rightly can told to match any/all values
of the supplied item.​

​David J

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message digoal 2016-02-23 03:29:16 BUG #13978: xmin,xmax not current for foreign table
Previous Message eshkinkot 2016-02-22 14:31:52 BUG #13977: Strange behavior with WAL archive recovery