I said:
> In most other contexts, we interpret such values as being in local time
> (the current server TimeZone) when it's necessary to make a distinction.
> Consistency would suggest doing it that way here too, I think.
I have applied a patch to make extract(epoch from timestamp) assume that
tim
[EMAIL PROTECTED] writes:
> I'm not sure whether this is actually a bug, but here goes: If you define a column
>as TIMESTAMP WITHOUT TIME ZONE (or TIMESTAMP(0) WITHOUT TIME ZONE), EXTRACT(EPOCH
>FROM column) returns a time stamp that is exactly one hour later than the time stamp
>from a column w
Jonas Bentzen (jonas at understroem dot dk) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
EXTRACT(EPOCH FROM column): Possible wrong output
Long Description
I'm not sure whether this is actually a bug, but here goes: If you define a column as
TI
