From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
Cc: | tgl(at)postgresql(dot)org, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql/src/include (config.h.in) |
Date: | 2000-12-10 20:03:01 |
Message-ID: | 200012102003.PAA00510@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
> > Don't cause --enable-cassert to define COPY_PARSE_PLAN_TREES automatically
> > anymore. That won't teach us anything new for the rest of this release
> > cycle, so it seems better to keep the --assert environment more like the
> > non-assert environment for beta.
> > 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?
>
> Is running enable-cassert on my production boxes going to cause
> a lot of overhead?
>
Assert adds about 7%, as I remember.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Alfred Perlstein | 2000-12-10 20:20:01 | Re: pgsql/src/include (config.h.in) |
Previous Message | Tom Lane | 2000-12-10 17:12:50 | Re: [COMMITTERS] pgsql/src/backend/commands (command.c vacuum.c) |