| From: | Mukesh Chhatani <chhatani(dot)mukesh(at)gmail(dot)com> |
|---|---|
| To: | 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:37:30 |
| Message-ID: | 1573670250461-0.post@n3.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
All,
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).
FYI.. default_statistics_target was set to 10000 but I changed it 100 and
even to 1000 and still planning time was high.
Still working on the dataset so that more people can investigate the issues.
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-11-13 18:42:13 | Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10 |
| Previous Message | Andres Freund | 2019-11-13 18:20:13 | Re: [BUG] Uninitializaed configOut.leafType used. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-11-13 18:42:13 | Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10 |
| Previous Message | David Fetter | 2019-11-13 18:12:16 | Re: Invisible PROMPT2 |