> > 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@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026