Re: [PATCH] pgpassfile connection option

From: Julian Markwort <julian(dot)markwort(at)uni-muenster(dot)de>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] pgpassfile connection option
Date: 2016-11-01 14:49:42
Message-ID: 5818AB86.5060706@uni-muenster.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Am 01.11.2016 um 15:14 schrieb Fabien COELHO:
>
>> Thus, when returning with an error, if conn->pgpassfile was set and a
>> password was necessary, we must have tried that pgpassfile, so i got
>> rid of the field "dot_pgpass_used"
>
> No, you should not have done that, because it changes a feature which
> was to warn *only* when the password was coming from file.
>
> The warning is wrong, the password was typed directly, not retrieved
> from a file. The "dot_pgpass_used" boolean is still required to avoid
> that.

I see... I was too focused on looking for things to declutter, that I
missed that case. I'll address that in the next revision.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2016-11-01 14:58:03 Re: auto_explain vs. parallel query
Previous Message Robert Haas 2016-11-01 14:31:49 Re: Proposal for changes to recovery.conf API