| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Mukesh Chhatani <chhatani(dot)mukesh(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10 |
| Date: | 2019-11-13 18:42:13 |
| Message-ID: | 20191113184213.yexnib6cbxpkmmwq@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hi,
On 2019-11-13 11:37:30 -0700, Mukesh Chhatani wrote:
> FYI.. default_statistics_target was set to 10000 but I changed it 100 and
> even to 1000 and still planning time was high.
Note that you'd need to ANALYZE the involved tables before that change
actually would effect planning time.
> Update I was able to resolve the problem by changing - partitioned tables to
> single table and changing data type of 2 columns used in the joins from
> varchar to varchar(50).
That's not going to be the fix. There's no efficiency difference between
those. It's more likely that, that the different statistics target would
have taken effect after the alter table etc.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-11-13 18:47:15 | Re: [BUG] Uninitializaed configOut.leafType used. |
| Previous Message | Mukesh Chhatani | 2019-11-13 18:37:30 | Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-11-13 18:50:47 | Re: Creating foreign key on partitioned table is too slow |
| Previous Message | Mukesh Chhatani | 2019-11-13 18:37:30 | Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10 |