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

From Adrian Klaver
Subject Re: Connect is not available, request timeout after 30000ms.
Date
Msg-id 86ad4a7f-5879-624e-c89a-ab9b6c19406b@aklaver.com
Whole thread Raw
In response to Re: Connect is not available, request timeout after 30000ms.  (Pawan Sharma <pawanpg0963@gmail.com>)
Responses Re: Connect is not available, request timeout after 30000ms.
List pgsql-general
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: Pawan Sharma
Date:
Subject: Re: Connect is not available, request timeout after 30000ms.
Next
From: Pawan Sharma
Date:
Subject: Re: Connect is not available, request timeout after 30000ms.