| From: | Howard Wells <mr284(at)protonmail(dot)com> |
|---|---|
| To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Condor <condor(at)stz-bg(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres SQLSTATE[08006] [7] timeout expired |
| Date: | 2019-08-25 21:59:23 |
| Message-ID: | NejU1rf6oEolnfmonxKZXVlxZ85kAklRpOCF469uv55IbqWQ6t8Rnrb8dImn_d0_nwI4qQt0tviV_dSSKUQ4AHPOyb-JyEutIEn7kpaWZSs=@protonmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I solved this problem. All four servers are behind a firewall, but port 5432 was not open on the firewall. When I opened 5432, the problem disappeared.
Thanks to Rob Sargent, Adrian Klaver and Condor for your help.
Howard
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, August 25, 2019 12:20 PM, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
> >>>>>
>
> > > > > > console.
> > > > > > The pg_hba.conf has these lines enabled:
> > > > > > pg_hba.conf:
> > > > > > host all [username] 0.0.0.0/0 trust
> > > > > > host all all 0.0.0.0/0 md5
> > > > > > host all all ::/0 md5
> > > > > > host all all all
>
> Who is encrypting the password?
>
> >
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-08-25 23:55:02 | Re: Postgres SQLSTATE[08006] [7] timeout expired |
| Previous Message | Tom Lane | 2019-08-25 20:27:48 | Re: For SELECT statement (just a reading one, no 'FOR UPDATE'), is COMMIT or ROLLBACK preferred? |