Skip site navigation (1) Skip section navigation (2)

Re: pgsql/src/include (config.h.in)

From: Alfred Perlstein <bright(at)wintelcom(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql/src/include (config.h.in)
Date: 2000-12-04 18:52:18
Message-ID: 20001204105217.W8051@fw.wintelcom.net (view raw or flat)
Thread:
Lists: pgsql-committers
* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [001204 08:00] wrote:
> Alfred Perlstein <bright(at)wintelcom(dot)net> writes:
> >> I'm going to leave CLOBBER_FREED_MEMORY and MEMORY_CONTEXT_CHECKING
> >> turned on by --enable-cassert for now, however.
> 
> > Urk, this looks pretty expensive, is there any flags available that
> > will enable the assertion checking without expensive memory zeroing
> > (or 0xdeadbeef'ing) free'd memory?
> 
> You can twiddle the declarations in config.h (or config.h.in).
> 
> > Is running enable-cassert on my production boxes going to cause
> > a lot of overhead?
> 
> While I haven't tried hard to measure it, the profiles that I've done
> don't show it as a huge cost.
> 
> In any case, you're not planning to run beta code as production,
> are you?

Nope, I'm using 7.0.3, but cassert and debug options have helped
us a lot in the past when tracking down bugs. :)

It would be helpful to have a extra sanity checking option that
doesn't do things like clear large blocks of memory.

-- 
-Alfred Perlstein - [bright(at)wintelcom(dot)net|alfred(at)freebsd(dot)org]
"I have the heart of a child; I keep it in a jar on my desk."

In response to

pgsql-committers by date

Next:From: Peter EisentrautDate: 2000-12-04 19:16:08
Subject: Re: pgsql (GNUmakefile.in)
Previous:From: Tom LaneDate: 2000-12-04 14:50:34
Subject: Re: pgsql/src/include (config.h.in)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group