Re: Rapid Seek Devices (feature request) - Mailing list pgsql-general

From Greg Stark
Subject Re: Rapid Seek Devices (feature request)
Date
Msg-id 407d949e0908171620h10e3ebe0tc5c2504cd9476cfe@mail.gmail.com
Whole thread Raw
In response to Re: Rapid Seek Devices (feature request)  (Jeremy Harris <jgh@wizmail.org>)
List pgsql-general
2009/8/17 Jeremy Harris <jgh@wizmail.org>:
> Could not pgsql *measure* these costs (on a sampling basis, and with long
> time-constants)?

In theory, sure. In practice, well, there are some engineering
challenges to solve.

1) The cost model isn't perfect so the it's not clear exactly what to
measure to get the best result. As the cost model stands now you would
have to include some of the cpu time as well as the i/o time.

2) Timing is expensive. On many platforms getting the current time
takes a long time and would make a big difference to the runtime of
the query.



--
greg
http://mit.edu/~gsstark/resume.pdf

pgsql-general by date:

Previous
From: Andrew Bartley
Date:
Subject: Re: Function Logging
Next
From: Bryan Murphy
Date:
Subject: Re: Failover, Wal Logging, and Multiple Spares