| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: roundoff problem in time datatype |
| Date: | 2005-09-26 17:21:21 |
| Message-ID: | 43382E11.30009@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
>
> Hm, so the proposal is "round unless that would produce 24:00:00, in
> which case truncate"? Seems a bit ugly but it would follow the letter
> of the spec, and avoid rejecting inputs that we used to accept. It's
> still not very clear what to do with '23:59:60.9' though.
I'd handle it the same; 23.59.60.9 -> 23.59.60 since this is apparently
a leap second. A normal second should never become a leap second from
some conversion, but a leap second should stay one.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-09-26 17:22:58 | Re: On Logging |
| Previous Message | Dann Corbit | 2005-09-26 17:17:26 | Re: [PERFORM] Releasing memory during External sorting? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2005-09-26 20:37:04 | Re: Patching dblink.c to avoid warning about open transaction |
| Previous Message | Tom Lane | 2005-09-26 17:00:21 | Re: roundoff problem in time datatype |