| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | cfederico87(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16053: Query planner performance regression in sql query with multiple CTE in v12 |
| Date: | 2019-10-12 17:17:21 |
| Message-ID: | 87eezhx5ck.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>>>>> "PG" == PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
PG> After upgrading to v12 from v11.4 I've noticed one of the queries
PG> run by an application has a significant performance degradation.
PG> I've managed to create a toy db that illustrates the issue.
PG> Following is a link of the db and the query in question (there
PG> seems to be no way to attach a file from the web form. If I should
PG> upload them somewhere else let me know)
PG> https://www.dropbox.com/s/6n3ctdn2zohoann/toy-db_and_query.zip?dl=0
You could at least have included the query in the message.
What seems to be happening here looks to me more down to chance than to
any bug. In v11, the join order is constrained by the CTEs, whereas in
v12 it is not; the misplan is the result of a mis-estimated 1-row result
from a subpath that may not have been considered under v11.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-10-13 00:10:32 | Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 |
| Previous Message | PG Bug reporting form | 2019-10-12 16:26:06 | BUG #16053: Query planner performance regression in sql query with multiple CTE in v12 |