| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | brian(at)omniti(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7626: Query planner never returns, uses 100% CPU |
| Date: | 2012-10-29 18:00:28 |
| Message-ID: | 21286.1351533628@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
brian(at)omniti(dot)com writes:
> Running this causes the thread to use 100% CPU and never returns (or at
> least not for longer than my patience runs out).
> This returns just fine on 8.4.1 and on 9.2beta.
Hmm ... seems to be a consequence of commit
3b8968f25232ad09001bf35ab4cc59f5a501193e. I wrote in that patch
+ * This looks expensive, but in practical cases there won't be very many
+ * distinct sets of outer rels to consider.
but evidently that was too optimistic :-(. Will need to think about
suitable heuristics for limiting the sets of outer relations we
consider building parameterized paths with.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-10-29 21:42:45 | Re: BUG #7623: Inconsistency on transaction isolation documentation |
| Previous Message | Bill MacArthur | 2012-10-29 17:08:56 | Re: BUG #7626: Query planner never returns, uses 100% CPU |