pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pepe TD Vo <pepevo@yahoo.com>
To: Steve Crawford <scrawford@pinpointresearch.com>
Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>
Cc: gilberto.castillo@etecsa.cu <gilberto.castillo@etecsa.cu>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
Date: Tue, 26 Feb 2019 21:09:49 +0000 (UTC)
Message-ID: <1259407684.5772133.1551215389418@mail.yahoo.com> (raw)
In-Reply-To: <CAEfWYyxGtO9ppUJyHJyOOHo5xin5vc5TBTf4r-bmkij_4f-DLw@mail.gmail.com>
References: <1766891885.5546566.1551195368839.ref@mail.yahoo.com>
	<1766891885.5546566.1551195368839@mail.yahoo.com>
	<CAGDYbUPdZDM_70O9wpZSD+EMRJJOyYO42VGAn3pj44br2H2cSg@mail.gmail.com>
	<1161831433.5624889.1551203198375@mail.yahoo.com>
	<713147705.5704638.1551207564863@mail.yahoo.com>
	<CAEfWYyxGtO9ppUJyHJyOOHo5xin5vc5TBTf4r-bmkij_4f-DLw@mail.gmail.com>

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@pinpointresearch.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 

   

view thread (24+ messages)  latest in thread

Message-ID: <1259407684.5772133.1551215389418@mail.yahoo.com>
Permalink:  ../1259407684.5772133.1551215389418@mail.yahoo.com/
Also on:    postgresql.org/message-id/1259407684.5772133.1551215389418@mail.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: pepevo@yahoo.com, scrawford@pinpointresearch.com, shreeyansh2014@gmail.com, gilberto.castillo@etecsa.cu, pgsql-admin@lists.postgresql.org
  Subject: Re: [MASSMAIL]Re: pg_dumpall: could not connect to database: FATAL
  In-Reply-To: <1259407684.5772133.1551215389418@mail.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox