| From: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
|---|---|
| To: | Mukesh Chhatani <chhatani(dot)mukesh(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10 |
| Date: | 2019-11-13 06:58:28 |
| Message-ID: | 25c7ebae-a3e9-5c79-23f6-cb183045d79b@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
13.11.2019 00:01, Mukesh Chhatani пишет:
> Thanks for getting back to me so quickly
>
> Queries are same and executed in 2 different environments. There are no
> long running queries on any of the environments since they are idle
> right away for my testing.
>
> I can try full vacuum if that is recommended since I tried vacuum
> analyze on the whole database in both environments.
>
> Datases have the same content and size is also same.
>
> Sorry but I am never seen this before , if the sizes vary or if the
> content varies I have seen execution time being slow and not the
> planning time.
>
> I am working on a dataset which I will share for further investigation
> and analysis.
Interesting. I will be waiting for your data set.
--
Andrey Lepikhov
Postgres Professional
https://postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 唯一★ | 2019-11-13 07:02:14 | 回复： BUG #16101: tables in the DB is not available after pg_restore |
| Previous Message | Fahar Abbas | 2019-11-13 06:19:28 | Re: BUG #16103: Initdb does not respect country for language |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-11-13 07:05:20 | Re: [PATCH] Do not use StdRdOptions in Access Methods |
| Previous Message | k.jamison@fujitsu.com | 2019-11-13 06:57:01 | RE: Recovery performance of DROP DATABASE with many tablespaces |