Could you run VACCUM ANALYZE.
From: Sterpu Victor <victor@xxxxxxxx>
Sent: Friday, November 22, 2019 2:46 PM
To: Fırat Güleç <firat.gulec@xxxxxxxxxxxx>
Cc: pgsql-performance@xxxxxxxxxxxxxxxxxxxx
Subject: Re[2]: Postgresql planning time too high
I did runned "VACCUM FULL" followed by "VACUUM" but no difference.
------ Original Message ------
From: "Fırat Güleç" <firat.gulec@xxxxxxxxxxxx>
To: "Sterpu Victor" <victor@xxxxxxxx>
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@xxxxxxxxxxxx
M: 0 532 210 57 18
İnönü Mh. Mimar Sinan Cd. No:3 Güzeller Org.San.Bölg. GEBZE / KOCAELİ
From: Sterpu Victor <victor@xxxxxxxx>
Sent: Friday, November 22, 2019 2:21 PM
To: pgsql-performance@xxxxxxxxxxxxxxxxxxxx
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
This is interesting because "VACUUM ANALYZE" solved the problem on postgresql 12.1, the planning time was cut down from 5165.742 ms to 517 ms.
This is great but I didn't think to do this on postgresql 12.1 because I did the same thing on the production server(postgresql 9.5) and the problem was not solved there by this command on the 9.5.
I guess I should update the production server.
Is there another way?
Thank you
------ Original Message ------
From: "Fırat Güleç" <firat.gulec@xxxxxxxxxxxx>
To: "Sterpu Victor" <victor@xxxxxxxx>
Sent: 2019-11-22 2:05:44 PM
Subject: RE: Re[2]: Postgresql planning time too high
