| From: | NTPT <ntpt(at)centrum(dot)cz> |
|---|---|
| To: | Jeremy Harris <jgh(at)wizmail(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Rapid Seek Devices (feature request) |
| Date: | 2009-08-17 22:34:44 |
| Message-ID: | 4A89DB04.80702@centrum.cz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
AFAIK postgresql measure characteristic of the data distribution in the
tables and indexes (that is what vacuum ANALYSE does) , but results of
that measures are **weighted by** random_page_cost and
sequential_page_cost. So measurements are correct, but costs (weight)
should reflect a real speed for sequentional and random operation of the
storage device(s) (tablespaces) involved.
Jeremy Harris napsal(a):
> On 08/17/2009 03:24 AM, Craig Ringer wrote:
>> On 16/08/2009 9:06 PM, NTPT wrote:
>>> So I suggest we should have "random_page_cost" and
>>> "Sequential_page_cost" configurable on per tablespace basis.
>>
>> That strikes me as a REALLY good idea, personally, though I don't know
>> enough about the planner to factor in implementation practicalities and
>> any cost for people _not_ using the feature.
>
> Could not pgsql *measure* these costs (on a sampling basis, and with long
> time-constants)?
>
> - Jeremy
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Bartley | 2009-08-17 22:42:35 | Re: Function Logging |
| Previous Message | Michael Clark | 2009-08-17 22:28:21 | PQgetlength vs. octet_length() |