Re: Rapid Seek Devices (feature request)

From: Greg Stark <gsstark(at)mit(dot)edu>
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 23:20:53
Message-ID: 407d949e0908171620h10e3ebe0tc5c2504cd9476cfe@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2009/8/17 Jeremy Harris <jgh(at)wizmail(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Nick 2009-08-17 23:33:11 Get most recent message between users?
Previous Message Andrew Bartley 2009-08-17 22:42:35 Re: Function Logging