Re: Postgresql planning time too high

Поиск
Список
Период
Сортировка
От Luís Roberto Weck
Тема Re: Postgresql planning time too high
Дата
Msg-id a4120d74-48d6-b54c-4ede-4ef209bf2bbf@siscobra.com.br
обсуждение исходный текст
Ответ на Re[2]: Postgresql planning time too high  ("Sterpu Victor" <victor@caido.ro>)
Список pgsql-performance
Em 22/11/2019 08:46, Sterpu Victor escreveu:
I did runned "VACCUM FULL" followed by "VACUUM" but no difference.

------ Original Message ------
From: "Fırat Güleç" <firat.gulec@hepsijet.com>
To: "Sterpu Victor" <victor@caido.ro>
Sent: 2019-11-22 1:35:15 PM
Subject: RE: Postgresql planning time too high

Hello Sterpu,

 

First, please run vaccum for your Postgresql DB.

 

No rows returned from your query. Could you double check your query criteria.

 

After that could you send explain analyze again .

 

Regards,

 

FIRAT GÜLEÇ 
Infrastructure & Database Operations Manager
firat.gulec@hepsijet.com

 

M: 0 532 210 57 18 
İnönü Mh. Mimar Sinan Cd. No:3 Güzeller Org.San.Bölg. GEBZE / KOCAELİ

image.png

 

 

 

From: Sterpu Victor <victor@caido.ro>
Sent: Friday, November 22, 2019 2:21 PM
To: pgsql-performance@lists.postgresql.org
Subject: Postgresql planning time too high

 

Hello

 

I'm on a PostgreSQL 12.1 and I just restored a database from a backup.

When I run a query I get a big execution time: 5.482 ms

After running EXPLAIN ANALYZE I can see that the "Planning Time: 5165.742 ms" and the "Execution Time: 6.244 ms".

The database is new(no need to vacuum) and i'm the only one connected to it. I use a single partition on the harddrive.

I also tried this on a postgresql 9.5 and the result was the same.

I'm not sure what to do to improve this situation.

The query and the explain is attached.

 

Thank you

 

Have you run the ANALYZE command to update your DB statistics?
Вложения

В списке pgsql-performance по дате отправления:

Предыдущее
От: Fırat Güleç
Дата:
Сообщение: RE: Re[2]: Postgresql planning time too high
Следующее
От: "Sterpu Victor"
Дата:
Сообщение: Re[4]: Postgresql planning time too high