| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql/src/backend/utils/cache (fcache.c) |
| Date: | 2000-08-11 19:19:34 |
| Message-ID: | Pine.BSF.4.21.0008111617250.54797-100000@thelab.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Fri, 11 Aug 2000, Tom Lane wrote:
> The Hermit Hacker <scrappy(at)hub(dot)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 :)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-08-11 23:45:28 | pgsql/src/backend/parser (gram.y analyze.c) |
| Previous Message | Tom Lane | 2000-08-11 19:15:28 | Re: pgsql/src/backend/utils/cache (fcache.c) |