From: | Pawan Sharma <pawanpg0963(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(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:43:28 |
Message-ID: | CAKqG8NW_xF1bbKExD_V2oaEaEgovcwyhNW0dS3qqUWn1cLo=cQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)klaver(at)aklaver(dot)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(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-06-25 15:59:56 | Re: psql UPDATE field [tab] expands to DEFAULT? |
Previous Message | Adrian Klaver | 2019-06-25 14:33:00 | Re: Connect is not available, request timeout after 30000ms. |