Re: now() and date_trunc() apparently corrupting data
| От | Tom Lane |
|---|---|
| Тема | Re: now() and date_trunc() apparently corrupting data |
| Дата | |
| Msg-id | 10087.1047596771@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | now() and date_trunc() apparently corrupting data (Oliver Elphick <olly@lfix.co.uk>) |
| Ответы |
Re: now() and date_trunc() apparently corrupting data
|
| Список | pgsql-bugs |
Oliver Elphick <olly@lfix.co.uk> writes:
> This is with -configure -enable-integer-datetime in 7.3.2, i386 Linux
> platform. Is anyone else seeing this? If so, does it happen without
> --enable-integer-datetime?
> junk=# select * from mt;
> v
> -------------
> 06:25:00+00
> (1 row)
> junk=# select * from mt where v < now();
> v
> -------------
> 00:00:00+00 <-- data has been changed...
> (1 row)
I think this is explained by this bug:
2003-02-13 12:04 tgl
* src/backend/utils/adt/date.c (REL7_3_STABLE): Prevent timetz2tm()
from scribbling on its input in HAVE_INT64_TIMESTAMP case.
Can you try it with CVS tip (either HEAD or REL7_3_STABLE branch)?
regards, tom lane
В списке pgsql-bugs по дате отправления: