| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: roundoff problem in time datatype |
| Date: | 2005-09-26 13:15:14 |
| Message-ID: | 23746.1127740514@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Dave Cramer <pg(at)fastcrypt(dot)com> writes:
> Actually, I think there is a case where 24:00 is a proper time. Isn't
> it used for adding leap seconds ?
No, I think the usual notation for a leap-second is '23:59:60'.
We do allow 60 in the seconds field for this purpose.
I suppose there's another possible approach, which is to special-case
the output of this value to look like '23:59:60' instead of '24:00:00'.
Then it could be reloaded. On the whole though, most people who came
across that behavior would probably think it's a bug...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-09-26 13:32:26 | Re: "expected authentication request from server, but received..." |
| Previous Message | Dave Cramer | 2005-09-26 12:58:54 | Re: roundoff problem in time datatype |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Bjorklund | 2005-09-26 14:16:09 | Re: roundoff problem in time datatype |
| Previous Message | Dave Cramer | 2005-09-26 12:58:54 | Re: roundoff problem in time datatype |