| From: | David Wheeler <dwheeler(at)dgitsystems(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>, Cameron Redpath <credpath(at)dgitsystems(dot)com> |
| Subject: | Re: Slow planning, fast execution for particular 3-table query |
| Date: | 2019-11-06 23:41:57 |
| Message-ID: | 42D20241-A10A-4A8C-A408-8E2326E37604@dgitsystems.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Is default_statistics_target set above default 100? I would assume that would reflect in the size of pg_statistic, but wanted to ask since increasing that from 100 to 1000 was the only time I have seen planning time explode. Are other queries slow to plan?
Looks like you’ve found it! Someone has set the target to 10k so that’s going to wildly increase planning time.
Thanks for your help! And thanks to the others who chipped in along the way 😊
Regards,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2019-11-07 00:15:30 | Re: Slow planning, fast execution for particular 3-table query |
| Previous Message | Andres Freund | 2019-11-06 23:15:53 | Re: FPGA optimization ... |