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

Re: pgsql/src/include (

From: Alfred Perlstein <bright(at)wintelcom(dot)net>
To: tgl(at)postgresql(dot)org
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql/src/include (
Date: 2000-12-04 06:56:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
* tgl(at)postgresql(dot)org <tgl(at)postgresql(dot)org> [001203 21:16] wrote:
>   Date: Saturday, December  2, 2000 @ 13:16:40
> Author: tgl
> Update of /home/projects/pgsql/cvsroot/pgsql/src/include
>      from
> Modified Files:
> -----------------------------  Log Message  -----------------------------
> 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.
> 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?

-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: Tom LaneDate: 2000-12-04 14:50:34
Subject: Re: pgsql/src/include (
Previous:From: tglDate: 2000-12-04 01:32:20
Subject: pgsql/contrib/vacuumlo (Makefile)

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