On Wed, Feb 22, 2006 at 04:46:35PM -0600, Scott Marlowe wrote:
> On Wed, 2006-02-22 at 16:36, John McCawley wrote:
> > Earlier this week when I logged into my database, I just so happened to
> > notice that the value for now() was six hours off of the time reported
> > by the operating system when using the date command from the command
> > line. How is this possible? I rebooted the server and the problem
> > magically went away. I am quite certain that I didn't modify anything
> > in the database that should cause this problem. It turns out that that
> > the now() time has been off for some time, and resulted in quite a bit
> > of corrupted data. What exactly should I do in the future to keep this
> > from happening, or where should I look for clues?
>
> Sounds like a time zone issue. I'd start looking there.
I've been bitten by this before as well. I'd be in favor of adding an
option such that postmaster would refuse to start if TZ was something
other than UTC; I'd much rather that then have a bunch of data get
screwed up...
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461