Re: password is no required, authentication is overridden

Andrew Hammond wrote:
>> Looking into the documentation delivered with pg ("PostgreSQL and
>> pgAdmin Help") there is a page about the pgpass file,
>> but there is not hint to environment variable pgpassword or the
>> pgpass-file on the page of pg_dump, maybe you can add it ?
>> In the documentation page of psql there is a hint to the pgpass file.
>>     
>
> That's a good idea. What do you think would be a good way to say it?
>
>   

see "+" for my text:


=> pg_dump

...
-U username
Connect as the given user

-W
Force a password prompt. This should happen automatically if the server 
requires password authentication.
+ You can also place your password in a .pgpass file in order to avoid 
any inputs (see Section 28.12, “The Password File”).

Environment

PGDATABASE

PGHOST

PGPORT

PGUSER
Default connection parameters.

Diagnostics
pg_dump internally executes SELECT statements. If you have problems 
running pg_dump, make sure you are able to select information from the 
database using, for example, psql.

Notes

+ In order to create nightly backups it might be necessary to run the 
authentication automatically.
+ Adding the password as a parameter to pg_dump is not supported because 
this appears in the process list, available to all local users.
+ Instead you can place your credentials in a .pgpass file (see Section 
28.12, “The Password File”).

If your database cluster has any local additions to the template1 
database, be careful to restore the ...



=> 28.12. The Password File

...
chmod 0600 ~/.pgpass. If the permissions are less strict than this, the 
file will be ignored. (The file permissions are not currently checked on 
Microsoft Windows, however.)

+ The .pgpass file will be automatically created if you're using pgAdmin 
III with "store password" being enabled in the connection settings.


bye
Thomas