Re: [PATCH] pgpassfile connection option - Mailing list pgsql-hackers

From Julian Markwort
Subject Re: [PATCH] pgpassfile connection option
Date
Msg-id 58115F2F.4010608@uni-muenster.de
Whole thread Raw
In response to Re: [PATCH] pgpassfile connection option  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: [PATCH] pgpassfile connection option  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
Thanks for your quick response, Fabien
> I think that PGPASSFILE is somehow checked twice
yup, that was unintended redundancy...
> I would suggest that the struct gets the value (from option, 
> environment or default) and is always used elsewhere. The 
> getPgPassFilename function should disappear and PasswordFromFile 
> should be simplified significantly. 
I agree, however that's easier said than done because the "default" is 
only constant by its definition, not by its location.
There is no "default" location as the home directory depends not only on 
the system but also on the user. Afaics we can't entirely get rid of a 
function to get the location of the default .pgpass file.

Kind regards,
Julian



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: 9.6, background worker processes, and PL/Java
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: Re: [RFC] Should we fix postmaster to avoid slow shutdown?