Re: Connect is not available, request timeout after 30000ms. - Mailing list pgsql-general

From Pawan Sharma
Subject Re: Connect is not available, request timeout after 30000ms.
Date
Msg-id CAKqG8NW_xF1bbKExD_V2oaEaEgovcwyhNW0dS3qqUWn1cLo=cQ@mail.gmail.com
Whole thread Raw
In response to Re: Connect is not available, request timeout after 30000ms.  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Ya this is because of ANALYZE.

now it's working fine.

Thanks for your support.


On Tue, Jun 25, 2019, 8:03 PM Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 6/25/19 7:24 AM, Pawan Sharma wrote:
> In PostgreSQL logs it's showing select queries are running with duration
> approx 37001.347ms
>

Is this normal?

Did you run ANALYZE on the database after you restored it to the new
Postgres 11 cluster?

If not do so.

Then run the query in psql or something similar with EXPALIN ANALYZE and
see what the time is.


I cannot find the error message string in the Postgres source code, so I
am guessing it came from somewhere else. Best guess is the app/driver
has a timeout set.


--
Adrian Klaver
adrian.klaver@aklaver.com

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Connect is not available, request timeout after 30000ms.
Next
From: Kevin Brannen
Date:
Subject: RE: Need a DB layout gui