| From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: possible wierd boolean bug? |
| Date: | 2004-12-15 20:50:50 |
| Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3412A756F@Herge.rcsinc.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> > I confirmed the problem on a linux server running beta3...so this
> > problem is quite reproducible by running the attached scripts on a
> > freshly loaded database.
>
> The attached patch fixes the problem for me.
>
> regards, tom lane
>
Yup. I just confirmed it from cvs. btw, the 4 rows I was complaining
about was due to my erroneously reading the analyze output, so
everything works ok now. Thanks!
Anyways, it would be nice to be able to use the sql row constructor to
do equality/comparison...wouldn't get caught writing such silly sql
statements :)
Merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-15 21:03:33 | Re: possible wierd boolean bug? |
| Previous Message | Ed L. | 2004-12-15 20:46:28 | Identifying time of last stat reset via sql |