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

Поиск
Список
Период
Сортировка
От Pawan Sharma
Тема Re: Connect is not available, request timeout after 30000ms.
Дата
Msg-id CAKqG8NW_xF1bbKExD_V2oaEaEgovcwyhNW0dS3qqUWn1cLo=cQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Connect is not available, request timeout after 30000ms.  (Adrian Klaver <adrian.klaver@aklaver.com>)
Список 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 по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: Connect is not available, request timeout after 30000ms.
Следующее
От: Kevin Brannen
Дата:
Сообщение: RE: Need a DB layout gui