Re: Postgresql planning time too high

From: Luís Roberto Weck <luisroberto(at)siscobra(dot)com(dot)br>
To: victor(at)caido(dot)ro
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Postgresql planning time too high
Date: 2019-11-22 12:22:16
Message-ID: a4120d74-48d6-b54c-4ede-4ef209bf2bbf@siscobra.com.br
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)gulec(at)hepsijet(dot)com
> <mailto:firat(dot)gulec(at)hepsijet(dot)com>>
> To: "Sterpu Victor" <victor(at)caido(dot)ro <mailto:victor(at)caido(dot)ro>>
> Cc: pgsql-performance(at)lists(dot)postgresql(dot)org
> <mailto:pgsql-performance(at)lists(dot)postgresql(dot)org>
> 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(dot)gulec(at)hepsijet(dot)com <mailto:firat(dot)gulec(at)hepsijet(dot)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(at)caido(dot)ro <mailto:victor(at)caido(dot)ro>>
>> *Sent:* Friday, November 22, 2019 2:21 PM
>> *To:* pgsql-performance(at)lists(dot)postgresql(dot)org
>> <mailto:pgsql-performance(at)lists(dot)postgresql(dot)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?

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Sterpu Victor 2019-11-22 12:25:10 Re[4]: Postgresql planning time too high
Previous Message Fırat Güleç 2019-11-22 12:05:44 RE: Re[2]: Postgresql planning time too high