| From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
|---|---|
| To: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Assert Levels |
| Date: | 2008-09-19 21:33:34 |
| Message-ID: | Pine.GSO.4.64.0809191729510.941@westnet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 19 Sep 2008, Greg Stark wrote:
> This is a good example of why running with assertions enabled on production
> might not be a good idea. But it's also a good example of why we should do
> our performance testing with assertions enabled if we can do it without
> invalidating the results.
The performance impact of assertions is large enough that I don't think
that goal is practical. However, issues like this do suggest that running
tests under a very heavy load like those used for performance testing
should sometimes be done with assertions on just to shake bugs out, even
if the actual performance results will be tossed.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2008-09-19 21:36:26 | Re: WIP patch: Collation support |
| Previous Message | Tom Lane | 2008-09-19 21:31:52 | Re: WIP patch: Collation support |