On Fri, 11 Aug 2000, Tom Lane wrote:
> The Hermit Hacker <scrappy@hub.org> writes:
> >> Ah ... it seems that someone has changed the behavior of assert checking
> >> to default to OFF, with no public notice or discussion. I think this is
> >> an extremely ill-considered change --- I will restore the old default
> >> behavior forthwith.
>
> > Huh? I thought Assert checking was always off by default until
> > --enable-cassert was set at configure time ... ?
>
> Right. But Peter added a run-time "debug_assertions" SET variable,
> which is cool except he made it default to OFF. So --enable-cassert
> wasn't enough to get assert checking anymore :-(. I changed the SET
> variable to default to ON.
that's what I was starting to think about as I asked, but figured it
wouldn't hurt to clarify :)
