| From: | Matthew Wakeling <matthew(at)flymine(dot)org> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | CPU cost of operators |
| Date: | 2009-09-30 17:12:29 |
| Message-ID: | alpine.DEB.2.00.0909301809250.19472@aragorn.flymine.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Episode umpteen of the ongoing saga with my GiST indexes.
For some reason, GiST uses loads of CPU. I have a query that runs entirely
out of cache, and it takes ages. This much I have tried to fix and failed
so far.
What I would now like to do is to tell postgres about it, so that the
EXPLAINs are correct. Is there a way to tell Postgres that an operator has
a large CPU cost? I can tell it what the join selectivity is, but I can't
find anything about CPU cost.
Matthew
--
Unfortunately, university regulations probably prohibit me from eating
small children in front of the lecture class.
-- Computer Science Lecturer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-09-30 20:13:29 | Re: CPU cost of operators |
| Previous Message | Ivan Voras | 2009-09-30 13:20:36 | Re: Bad performance of SELECT ... where id IN (...) |