Re: Connect is not available, request timeout after 30000ms.

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Pawan Sharma <pawanpg0963(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Connect is not available, request timeout after 30000ms.
Date: 2019-06-25 14:33:00
Message-ID: 86ad4a7f-5879-624e-c89a-ab9b6c19406b@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pawan Sharma 2019-06-25 14:43:28 Re: Connect is not available, request timeout after 30000ms.
Previous Message Pawan Sharma 2019-06-25 14:24:02 Re: Connect is not available, request timeout after 30000ms.