| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Link <dlink(at)soundscan(dot)com> |
| Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: IS NULL |
| Date: | 2001-11-07 20:31:27 |
| Message-ID: | 6387.1005165087@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
David Link <dlink(at)soundscan(dot)com> writes:
>> This is a bug. What version are you using? Could you supply
>> an exact example of a value that makes it crash?
> pg 7.0.3 (running on mandrake 8.0 / 2.4.3 kernal)
Okay, I've looked at the CVS logs and I believe you are stumbling over
some nasty little bugs in the 7.0.* versions of to_timestamp (which is
invoked by to_date) and to_char. I would strongly recommend an upgrade
to 7.1.*. In particular, 7.0's to_timestamp has the ugly habit of
scribbling on its input data, which is bad news in any case but
particularly so when applied directly to a table column :-(. If you
use it in 7.0 you are very likely to suffer unrecoverable data loss.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-07 20:41:37 | Re: Index not used on single select, but used in join. |
| Previous Message | Francisco Reyes | 2001-11-07 20:10:46 | Index not used on single select, but used in join. |