[EMAIL PROTECTED] writes:
> Creating database system directory /usr/local/pgsql/data
> Creating database system directory /usr/local/pgsql/data/base
> Creating database XLOG directory /usr/local/pgsql/data/pg_xlog
> Creating template database in /usr/local/pgsql/data/base/template1
> ERROR: Erro
> Long Description
> I use expression like int4(reltime()) to get interval length in
>seconds. When is NULL backend crashes (psql session):
This is likely fixed in the upcoming 7.1, since NULL handling has been
greatly improved for "by value" types like reltime. However, you *could*
be doing th
> When postgresql converts string representation of date to timestamp, he make one
>minute back error. Any insert or update with string date representation damage real
>value of date!
> BUT if you use string date representation without time part, your data will be
>shifted one day back!!!
> Tes
Tomas Dobrovolny ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
result of conversion to timestamp is shifted 1 minute back
Long Description
When postgresql converts string representation of date to timestamp, he make one
minu
Dmitry Tsitelov ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
reltime with NULL fields crashes backend
Long Description
I use expression like int4(reltime()) to get interval length in
seconds. When is NULL backend crashes (