Dear Tom, dear Kevin
In fact "show integer_datetimes;" returns "off". As such there is a perfect
reason for this rounding. I assumed wrongly this being a bug. Sorry :-)
I understand as well your arguments on why not to use such a value for
infinity. The reason why I used it was because I ported t
"Kevin Grittner" writes:
> "Matthias" wrote:
>> It is about when using a upper-boundary timestamp. The value of
>> -12-31 23:59:59.99 is sometimes used to indicate an infinite
>> validity.
> One other thought -- using a "magic value" for something like this is
> usually a bad idea. NUL
"Matthias" wrote:
> It is about when using a upper-boundary timestamp. The value of
> -12-31 23:59:59.99 is sometimes used to indicate an infinite
> validity.
One other thought -- using a "magic value" for something like this is
usually a bad idea. NULL indicates the absence of a valu
"Matthias" wrote:
> I noticed an unusual (and from my point of view inconsistent)
> rounding of a timestamp:
What do you get when you run?:
show integer_datetimes;
If it is off, which is probably the default for your distribution
under 8.3.X, timestamps are floating point (approximate) val
The following bug has been logged online:
Bug reference: 4960
Logged by: Matthias
Email address: matthias.ce...@gmail.com
PostgreSQL version: 8.3.7
Operating system: Windows XP
Description:Unexpected timestamp rounding
Details:
Dear developers,
I noticed an unusual
