Re: A costing analysis tool - Mailing list pgsql-hackers

From Tom Lane
Subject Re: A costing analysis tool
Date
Msg-id 7416.1129323653@sss.pgh.pa.us
Whole thread Raw
In response to A costing analysis tool  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Dang.  Obviously, that's inverted.  Also, I'd need to
> factor in the setup time.  Bother.  Are you sure we can't
> just make sure the test scripts operate against tables
> with accurate statistics?

Well, the point of my comment was that you should record the rowcounts
so that you know whether or not a particular test case was skewed by
inaccurate stats.  Whether you choose to disregard those cases or try
to include them in the analysis is up to you --- but assuming that every
number submitted to you is unaffected by bad stats is just asking for
trouble.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: A costing analysis tool
Next
From: Neil Conway
Date:
Subject: Re: Open items