| 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 18:25:21 |
| Message-ID: | Pine.BSF.4.21.0008111524260.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:
> I said:
> > "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> >> Seems the Assert() fails in misc regression test at
> >> SELECT p.name, p.hobbies.name FROM person* p;.
>
> > Really? It does not fail for me (else I'd certainly not have
> > committed the patch this way).
>
> 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 ... ? its been that way for as
long as I can remember ... or are we talking abuot a 'post
--enable-cassert configured' compile, using our config file?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-08-11 18:31:09 | pgsql/doc/src/sgml (runtime.sgml) |
| Previous Message | Tom Lane | 2000-08-11 18:18:07 | Re: pgsql/src/backend/utils/cache (fcache.c) |