Description of problem:
$subject. E.g. setting PGPASSWORD to a wrong value makes pg_dump try it even though we create a temporary pgpass file and set PGPASSFILE.
Version-Release number of selected component (if applicable):
Since 3.3 I think
Steps to Reproduce:
1. export PGPASSWORD=wrongpass
After exporting PGPASSWORD with a wrong pass the engine-backup is completed successfully.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.