Re: [PATCH] pgpassfile connection option
Julian Markwort <julian.markwort@uni-muenster.de>
From: Julian Markwort <julian.markwort@uni-muenster.de>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2016-11-01T14:49:42Z
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.
Commits
-
Allow password file name to be specified as a libpq connection parameter.
- ba005f193d88 10.0 landed