| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Marinos J(dot) Yannikos" <mjy(at)geizhals(dot)at> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: why do optimizer parameters have to be set manually? |
| Date: | 2003-12-18 19:56:20 |
| Message-ID: | 22686.1071777380@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Marinos J. Yannikos" <mjy(at)geizhals(dot)at> writes:
> it seems to me that the optimizer parameters (like random_page_cost
> etc.) could easily be calculated and adjusted dynamically be the DB
> backend based on the planner's cost estimates and actual run times for
> different queries. Perhaps the developers could comment on that?
No, they are not that easy to determine. In particular I think the idea
of automatically feeding back error measurements is hopeless, because
you cannot tell which parameters are wrong.
> I'm not sure how the parameters are used internally (apart from whatever
> "EXPLAIN" shows), but if cpu_operator_cost is the same for all
> operators, this should probably also be adjusted for individual
> operators (I suppose that ">" is not as costly as "~*").
In theory perhaps, but in practice this is far down in the noise in most
situations.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2003-12-18 23:18:48 | is it possible to get the optimizer to use indexes with a like clause |
| Previous Message | Conny Thimren | 2003-12-18 19:43:29 | general performance question |