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

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

Предыдущее
От: Pawan Sharma
Дата:
Сообщение: Re: Connect is not available, request timeout after 30000ms.
Следующее
От: Pawan Sharma
Дата:
Сообщение: Re: Connect is not available, request timeout after 30000ms.