Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL

I typo PORT without =
yes, I did reload postgres after make a configuration change.
v/r,

 Bach-Nga

No one in this world is pure and perfect.  If you avoid people for their mistakes you will be alone. So judge less, love and forgive more.To call him a dog hardly seems to do him justice though in as much as he had four legs, a tail, and barked, I admit he was, to all outward appearances. But to those who knew him well, he was a perfect gentleman (Hermione Gingold)
**Live simply **Love generously **Care deeply **Speak kindly.*** Genuinely rich *** Faithful talent *** Sharing success

On Tuesday, February 26, 2019 3:55 PM, Steve Crawford <scrawford(at)pinpointresearch(dot)com> wrote:

Some random observations that may or may not be of use.
Are you making sure to reload PostgreSQL whenever you make a config change?

I also found pg_hba.conf on both folders  /var/lib/pgsql/11/data/pg_hba.conf & /var/lib/pgsql/data/pg_hba.conf).  I modified it as above and the script is not working even run from the command prompt.

To find out which pg_hba.conf file your running database is using run:
show all;
Then search for hba_file or view directly by:
select setting from pg_settings where name = 'hba_file';

You can verify your pg_hba.conf settings with (as user postgres):
select * from pg_hba_file_rules ; 
# export HOSTNAME=hostname
# export USERNAME=postgres# export DATABASE=postgres # export PORT 5432# pg_dump -v -p $PORT -U $USERNAME -d $DATABASE -f /tmp/postgresbakup.sql

Looks like you are missing the "=" between PORT and 5432
Cheers,Steve