| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sean Chittenden <sean(at)chittenden(dot)org> |
| Cc: | Thomas Lockhart <lockhart(at)fourpalms(dot)org>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Bug #630: date/time storage problem: timestamp parsed |
| Date: | 2002-04-10 04:26:43 |
| Message-ID: | 1372.1018412803@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Sean Chittenden <sean(at)chittenden(dot)org> writes:
> Looks like it's a "bug" in mktime() on FreeBSD: it doesn't seem to do
> so well with invalid times that happen between daylight savings
> time... or is that a postgres thing for not kicking up an error (out
> of bounds time)? Or should 2am PST be converted to 3am? -sc
We've seen a *lot* of problems on various platforms with mktime
misbehaving on corner cases ... although I have to admit that failures
in PST/PDT zone are a new one on me (at least from an American
perspective, that ain't exactly a corner case). The
DetermineLocalTimeZone() routine in datetime.c is supposed to try to
defend against the more common forms of mktime brain-damage. Perhaps
you can suggest a way of improving it to work around this FreeBSD
problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Chittenden | 2002-04-10 04:44:42 | Re: Bug #630: date/time storage problem: timestamp parsed |
| Previous Message | Michael Loftis | 2002-04-10 02:51:47 | Re: Bug #630: date/time storage problem: timestamp parsed |