| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
| Cc: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Assert Levels |
| Date: | 2008-09-20 06:25:09 |
| Message-ID: | 1221891909.4445.69.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2008-09-19 at 17:33 -0400, Greg Smith wrote:
> 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
The starting point of this was that the *current* performance impact of
assertions is large enough that we turn them off.
> that I don't think that goal is practical.
So we can't use that as an argument against doing something to enable
the lighter checks in certain circumstances in the future.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-09-20 06:25:21 | Re: Assert Levels |
| Previous Message | Russell Smith | 2008-09-20 05:00:22 | Re: Where to Host Project |