Back to my original question, though. Any ideas why it is still prompting for password even though it had ‘trust’ in the pg_hba.conf? The .pgpass or the PGPASSWORD is only a work-around for that, I think. ‘Trust’ is supposed to:
Allow the connection unconditionally. This method allows anyone that can connect to the PostgreSQL database server to login as any PostgreSQL user they wish, without the need for a password or any other authentication
So, I shouldn’t need to set-up .pgpass or PGPASSWORD.
Any thoughts?
Do you use any connection pool (pgbouncer)?
Pg_dumpall command is being running within the server? or you are connecting to another machine?
The best is you pass the command that you are running and also show your pg_hba.conf
if you are running from within the own server and want to let the pg_hba in trust for local connections
your pg_hba.conf this like this?
# Socket and localhost place all all trust host all all 127.0.0.1/32 trust
Remember you have to connect the port of the postmaster