Any reason why postgres can't detect time zone on my machine automatically?
LOG: could not recognize system timezone, defaulting to Etc/GMT-8
HINT: You can specify the correct timezone in postgresql.conf.
postmaster starting
-bash-2.05b$ LOG: database system was shut down at 2004-05-31 15:19:00
Christopher Kings-Lynne writes:
Any reason why postgres can't detect time zone on my machine
automatically?
LOG: could not recognize system timezone, defaulting to Etc/GMT-8
HINT: You can specify the correct timezone in postgresql.conf.
postmaster starting
-bash-2.05b$ LOG: database
Any reason why postgres can't detect time zone on my machine
automatically?
I'm guessing the TZ code isn't identifying Aussie timezones. I'm getting the
same message, albeit Etc/GMT-10. If anyone who hacked on the TZ code
(Magnus, Bruce, ...) wants me to add a few printfs to trace this down,
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Any reason why postgres can't detect time zone on my machine
automatically?
I'm guessing the TZ code isn't identifying Aussie timezones.
So what *is* your zone, exactly? I don't see how you expect us to
figure out why it's not matching when
So what *is* your zone, exactly? I don't see how you expect us to
figure out why it's not matching when we don't know what it's not
matching.
In my case, one of these should be right:
DEBUG: Reject TZ Australia/NSW: at 1086048000 EST versus AUS Eastern
Standard Time
DEBUG: Reject TZ
Claudio Natoli [EMAIL PROTECTED] writes:
In my case, one of these should be right:
DEBUG: Reject TZ Australia/NSW: at 1086048000 EST versus AUS Eastern
Standard Time
DEBUG: Reject TZ Australia/Sydney: at 1086048000 EST versus AUS
Eastern Standard Time
Hm, is this a Windows box? We
Tom Lane writes:
Hm, is this a Windows box? We already suspected that we'd
have to fudge on matching the timezone abbreviations on Windows ..,
In my case, yes, Win XP.
Cheers,
Claudio
---
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these