| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: A costing analysis tool |
| Date: | 2005-10-14 21:00:53 |
| Message-ID: | 7416.1129323653@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2005-10-14 21:42:44 | Re: Open items |
| Previous Message | Kevin Grittner | 2005-10-14 20:50:31 | Re: A costing analysis tool |