Re: Discarding the resulting rows

От:

Tom Lane <tgl@sss.pgh.pa.us>

Дата:

26 апреля 2010 г. в 17:25:47

Re: Discarding the resulting rows

От:

"Murali M. Krishna" <murali1729@yahoo.com>

Дата:

26 апреля 2010 г. в 20:41:00

Hello All:

The optimizer assumes that data is disk resident when computing the cost of a query plan.
I am trying to ascertain what the correlation is between times and costs of some benchmark queries to see how good the cost model is.

Since I have more than 100 queries, it would be painful to stop and start the server each time to force all the buffer pages out. Also, some of these queries have large number of result rows. I don't want the time to be skewed by the output time.

Cheers,

Murali.

-----------------------------------------------------------------
Please visit NumberFest.com for educational number puzzles & mind exercises for all ages! And please tell your friends about it. Thank You!

--- On Mon, 4/26/10, Tom Lane <tgl@sss.pgh.pa.us> wrote:

From: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: [HACKERS] Discarding the resulting rows
To: "Jaime Casanova" <jcasanov@systemguards.com.ec>
Cc: "Robert Haas" <robertmhaas@gmail.com>, "Kevin Grittner" <Kevin.Grittner@wicourts.gov>, pgsql-hackers@postgresql.org, "Murali M. Krishna" <murali1729@yahoo.com>
Date: Monday, April 26, 2010, 1:25 PM

Jaime Casanova <jcasanov@systemguards.com.ec> writes:
> On Mon, Apr 26, 2010 at 3:03 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Mon, Apr 26, 2010 at 3:36 PM, Kevin Grittner
>> <Kevin.Grittner@wicourts.gov> wrote:
>>> I would use EXPLAIN ANALYZE SELECT ...
>>
>> There's some overhead to that, of course.

> he could see the "actual time" in the very first row of the EXPLAIN
> ANALYZE... isn't that a value that is more close to what the OP is
> looking for?

Well, it will include the instrumentation overhead of EXPLAIN ANALYZE,
which can be nontrivial depending on your hardware and the query plan.

On the other hand, EXPLAIN skips the cost of converting the result data
to text form, not to mention the network overhead of delivering it; so
in another sense it's underestimating the work involved.

I guess the real question is exactly what the OP is hoping to measure
and why.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers