Re: [HACKERS] .pgpass's behavior has changed

2017-05-09 Thread Kyotaro HORIGUCHI
At Mon, 1 May 2017 11:34:41 -0400, Robert Haas wrote in > On Fri, Apr 28, 2017 at 3:54 AM, Kyotaro HORIGUCHI > wrote: > > But the above also leaves a bug so I sent another patch to fix > > it. The attched patch restores the 9.6's beavior of looking up > > .pgpass file in the same manner to the

Re: [HACKERS] .pgpass's behavior has changed

2017-05-01 Thread Robert Haas
On Fri, Apr 28, 2017 at 3:54 AM, Kyotaro HORIGUCHI wrote: > But the above also leaves a bug so I sent another patch to fix > it. The attched patch restores the 9.6's beavior of looking up > .pgpass file in the same manner to the aother patch. Thanks for catching this. Committed. -- Robert Haas

Re: [HACKERS] .pgpass's behavior has changed

2017-04-30 Thread Noah Misch
On Fri, Apr 28, 2017 at 04:54:32PM +0900, Kyotaro HORIGUCHI wrote: > I noticed that the precedence between host and hostaddr in a > connection string is reversed in regard to .pgpass lookup in > devel. > > For example the following connection string uses a .pgpass entry > with "127.0.0.1", not "ho

Re: [HACKERS] .pgpass's behavior has changed

2017-04-28 Thread Michael Paquier
On Fri, Apr 28, 2017 at 4:54 PM, Kyotaro HORIGUCHI wrote: > I noticed that the precedence between host and hostaddr in a > connection string is reversed in regard to .pgpass lookup in > devel. > > For example the following connection string uses a .pgpass entry > with "127.0.0.1", not "hoge". > >

[HACKERS] .pgpass's behavior has changed

2017-04-28 Thread Kyotaro HORIGUCHI
Hello. I noticed that the precedence between host and hostaddr in a connection string is reversed in regard to .pgpass lookup in devel. For example the following connection string uses a .pgpass entry with "127.0.0.1", not "hoge". "host=hoge hostaddr=127.0.0.1 port=5432 dbname=postgres" This c