> No, the behavior is not platform-specific. I'm on HP-PA:
Hmm. Don't see that on my Linux box :(
We don't have regression tests which cover this case?
> The problem is that we round the fractional seconds part to two digits
> only after we've separated seconds from the other fields. (I imagi
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> The original report did not give complete platform details, but in
> my recollection the *only* recent cases of this display problem come
> from Mandrake systems which are built with overly aggressive compiler
> optimization options.
No, the behavior
> > It seems that there is a problem when retrieving a timestamp value (rounding).
> > NO minute has 61 seconds. Am I wrong?
> > radius=# select timestamp 'Tue 23 Jan 21:38:59.997 2001';
> > -
> > Tue 23 Jan 21:38:60.00 2001 ART
> Actually, such leap-seconds are p
> Gonzalo Arana wrote:
>> radius=# create table x (x timestamp);
>> CREATE
>> radius=# insert into x (x) values ('Tue 23 Jan 21:38:59.997 2001');
>> INSERT 619178 1
>> radius=# select * from x;
>> x
>> -
>> Tue 23 Jan 21:38:60.00 2001 ART
>> (1 row)
This is just a
Gonzalo Arana wrote:
>
>
> POSTGRESQL BUG REPORT TEMPLATE
>
>
> Your name : Gonzalo Arana
> Your email addres
On Wed, Jan 24, 2001 at 05:50:24PM -0300,
Gonzalo Arana <[EMAIL PROTECTED]> wrote:
>
> It seems that there is a problem when retrieving a timestamp value (rounding).
>
> NO minute has 61 seconds. Am I wrong?
When leap seconds occur, minutes can have 61 seconds.
