Re: Bug #630: date/time storage problem: timestamp parsed - Mailing list pgsql-bugs

From Thomas Lockhart
Subject Re: Bug #630: date/time storage problem: timestamp parsed
Date
Msg-id 3CB3DD28.B4FF07C8@fourpalms.org
Whole thread Raw
In response to Bug #630: date/time storage problem: timestamp parsed incorrectly...  (pgsql-bugs@postgresql.org)
Responses Re: Bug #630: date/time storage problem: timestamp parsed  (Sean Chittenden <sean@chittenden.org>)
List pgsql-bugs
...
> Good call Tom.  ...  I'm going to file a PR w/ FreeBSD.  I know the
> attached patch is something of a hack, but it works.  I'm not totally
> wild about altering the original time object, but I don't know that I
> have a choice in this case.  Does anyone switch timezones and only
> adjust their clocks by anything other than 60min?  I seem to recall
> that happening in a few places, but the patch isn't any worse than
> where we are now. ::shrug:: This look like an okay patch?

Yuck. You are trying the right things, but I'm not sure that we should
allow mktime() to fail for special cases like this. Falling back to GMT
(a potential offset of up to 12 hours from what was intended by the
user) is (perhaps) unacceptably ugly, particularly for recent/current
epochs which would be reasonably expected to behave correctly.

I'm inclined to test for an error return from mktime(), or to test it as
an ASSERT(), and then throw an error, rather than passing along
garbaged-up values.

Comments?

                        - Thomas

pgsql-bugs by date:

Previous
From: Sean Chittenden
Date:
Subject: Re: Bug #630: date/time storage problem: timestamp parsed
Next
From: Sean Chittenden
Date:
Subject: Re: Bug #630: date/time storage problem: timestamp parsed