| From: | Matthew Wakeling <matthew(at)flymine(dot)org> |
|---|---|
| To: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Really dumb planner decision |
| Date: | 2009-04-16 11:24:42 |
| Message-ID: | alpine.DEB.2.00.0904161222310.4053@aragorn.flymine.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 16 Apr 2009, Grzegorz Jaśkiewicz wrote:
> On a second look, it looks like you are are joining that view twice,
> at this point, I have no idea myself what it might be. But I guess it
> has to search over 5M rows for each of 105 in other query.
>
> I wonder what more experienced guys here will have to say about it.
That view appears as a two-column table, so I have joined something on
both of those columns, yes.
Interestingly, joining the dataset table breaks the query plan, but that
table only has 77 rows, and it is joined on by its unique primary key
index. That should be really trivial for Postgres to do.
Matthew
--
I quite understand I'm doing algebra on the blackboard and the usual response
is to throw objects... If you're going to freak out... wait until party time
and invite me along -- Computer Science Lecturer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Wakeling | 2009-04-16 11:31:42 | Re: Really dumb planner decision |
| Previous Message | Grzegorz Jaśkiewicz | 2009-04-16 11:16:13 | Re: Really dumb planner decision |