Can't detect time zone

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 system was shut down at
2004-05-31 15:19:00
GMT-8
LOG: checkpoint record is at 0/A47C80
LOG: redo record is at 0/A47C80; undo record is at 0/0; shutdown TRUE
LOG: next transaction ID: 536; next OID: 17218
LOG: database system is ready

-bash-2.05b$ date
Mon May 31 15:21:10 WST 2004

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, pleae
get in touch with me.

Cheers,
Claudio

--- 
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see 
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>

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, pleae
get in touch with me.

Yeah, I set australian_timezones to true in my postgresql.conf and it
still fails.

Chris

Christopher Kings-Lynne <chriskl@familyhealth.com.au> 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 we don't know what it's not
matching.

There already are some debug printouts in CVS tip. If you set
log_min_messages to debug4 or debug5 you should get reams of
log messages about why each tested TZ setting didn't seem to match
the system's timezone. If you could send along the output for
the zones that seem like reasonable candidates to match, it'd help.

regards, tom lane

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 "Australia/Sydney": at 1086048000 "EST" versus "AUS
Eastern Standard Time"

I imagine Christopher ought to be matching one of these two; presumably with
an error message as per above except with "WST" and "Western".

DEBUG: Reject TZ "Australia/Perth": at 1086048000 2004-06-01 08:00:00 std
versus 2004-06-01 10:00:00 std
DEBUG: Reject TZ "Australia/West": at 1086048000 2004-06-01 08:00:00 std
versus 2004-06-01 10:00:00 std

Cheers,
Claudio

--- 
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see 
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>

Claudio Natoli <claudio.natoli@memetrics.com> 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 already suspected that we'd have to fudge
on matching the timezone abbreviations on Windows ..,

regards, tom lane

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 disclaimers and policies see 
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>