| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | John McCawley <nospam(at)hardgeus(dot)com> |
| Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: now() time off |
| Date: | 2006-02-22 22:46:35 |
| Message-ID: | 1140648395.5777.48.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-02-23 00:35:55 | Re: now() time off |
| Previous Message | John McCawley | 2006-02-22 22:36:43 | now() time off |