From: Sterpu Victor <victor@caido.ro>
To: Fırat Güleç <firat.gulec@hepsijet.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re[4]: Postgresql planning time too high
Date: Fri, 22 Nov 2019 12:44:27 +0000
Message-ID: <em26503cdb-24f1-4d95-bb80-63f05b7362f0@victor-pc> (raw)
In-Reply-To: <6c4f362a349e68f014250b2649a596a3@mail.gmail.com>
References: <emd93eb533-aade-42ef-8609-2dccab1463d4@victor-pc>
<7ca4228bd9ea8ee1b119123679f340ff@mail.gmail.com>
<ema9d2726b-a01b-4f5d-816d-84c8ffbe509e@victor-pc>
<6c4f362a349e68f014250b2649a596a3@mail.gmail.com>
I'm sorry, I messed up between a lot of queries ..... there is no
difference after running "VACUUM ANALYZE".
I guess this was to be expected as the database was just restored from
backup.
------ Original Message ------
From: "Fırat Güleç" <firat.gulec@hepsijet.com>
To: "Sterpu Victor" <victor@caido.ro>
Cc: pgsql-performance@lists.postgresql.org
Sent: 2019-11-22 2:05:44 PM
Subject: RE: Re[2]: Postgresql planning time too high
>Could you run VACCUM ANALYZE.
>
>
>
>From: Sterpu Victor <victor@caido.ro>
>Sent: Friday, November 22, 2019 2:46 PM
>To: Fırat Güleç <firat.gulec@hepsijet.com>
>Cc:pgsql-performance@lists.postgresql.org
>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@hepsijet.com>
>
>To: "Sterpu Victor" <victor@caido.ro>
>
>Cc: pgsql-performance@lists.postgresql.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.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İ
>>
>>
>>
>>
>>
>>
>>
>>
>>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
>>
>>
>>
Attachments:image001.png (image/png, 10.3K) downloadview image
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: victor@caido.ro, firat.gulec@hepsijet.com, pgsql-performance@lists.postgresql.org
Subject: Re: Re[4]: Postgresql planning time too high
In-Reply-To: <em26503cdb-24f1-4d95-bb80-63f05b7362f0@victor-pc>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox