LOG: database system was shut down at 2004-05-25 15:15:44 GMT-12
For comparison, 7.4.1 on the same system says:
LOG: database system was shut down at 2004-05-25 16:03:43 NZST
Can we keep the zic database convention unchanged but change the display
format in the logs to be
Zeugswetter Andreas SB SD wrote:
LOG: database system was shut down at 2004-05-25 15:15:44 GMT-12
For comparison, 7.4.1 on the same system says:
LOG: database system was shut down at 2004-05-25 16:03:43 NZST
Can we keep the zic database convention unchanged but change the display
format in
Oliver Jowett wrote:
Tom Lane wrote:
Oliver Jowett [EMAIL PROTECTED] writes:
Also, unless I'm missing something, shouldn't Chile (Alvaro's timezone?)
be behind GMT (GMT-something) not ahead of it (GMT+something)?
Part of the confusion here is that the zone names in the zic
Zeugswetter Andreas SB SD [EMAIL PROTECTED] writes:
It is common practice that + is East and - is West, no ?
The SQL standard says that. The POSIX standard says the opposite.
Most of the Unixen I'm familiar with follow POSIX when choosing time
zone names.
The zic database is in itself a de
I wrote:
Also, it's worth pointing out here that falling back to Etc/GMT+/-n
is intended to be just that, a last-ditch fallback that won't be seen
in normal practice. We still need to do some more work on
identify_system_timezone() to make that happen outside North America,
but I would like
Oliver Jowett [EMAIL PROTECTED] writes:
Yes, exactly. Regardless of how the timezone is handled internally, showing
12-hours-east as GMT-12 in logs is horribly confusing.
Well, uh, you could always just pretend it was really 12-hours-west...
That doesn't help people in other time zones though
On Tue, May 25, 2004 at 03:01:24PM -0400, Tom Lane wrote:
I wrote:
Also, it's worth pointing out here that falling back to Etc/GMT+/-n
is intended to be just that, a last-ditch fallback that won't be seen
in normal practice. We still need to do some more work on
Tom Lane wrote:
BTW, as of an hour or so ago, identify_system_timezone is a bit smarter
than before. Please try it and see if it gets it right on your machine.
Looks good:
LOG: database system was shut down at 2004-05-26 12:43:55 NZST
test=# select now();
now
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
First I initdb'd without TZ set. So every time I start the server I get
LOG: could not recognize system timezone, defaulting to Etc/GMT-4
HINT: You can specify the correct timezone in postgresql.conf.
I've fixed the minor issue here,
Oliver Jowett [EMAIL PROTECTED] writes:
Also, unless I'm missing something, shouldn't Chile (Alvaro's timezone?)
be behind GMT (GMT-something) not ahead of it (GMT+something)?
Part of the confusion here is that the zone names in the zic database
follow POSIX rules: plus is west of Greenwich.
Tom Lane wrote:
Oliver Jowett [EMAIL PROTECTED] writes:
Also, unless I'm missing something, shouldn't Chile (Alvaro's timezone?)
be behind GMT (GMT-something) not ahead of it (GMT+something)?
Part of the confusion here is that the zone names in the zic database
follow POSIX rules: plus is west
Oliver Jowett [EMAIL PROTECTED] writes:
What confused me is that the times in the log don't follow the
SQL-and-everything-else convention:
LOG: database system was shut down at 2004-05-25 15:15:44 GMT-12
For comparison, 7.4.1 on the same system says:
LOG: database system was shut
I'm looking at the new timezone support.
First I initdb'd without TZ set. So every time I start the server I get
LOG: could not recognize system timezone, defaulting to Etc/GMT-4
HINT: You can specify the correct timezone in postgresql.conf.
Obviously the setup is wrong because DST doesn't
Alvaro Herrera [EMAIL PROTECTED] writes:
First I initdb'd without TZ set. So every time I start the server I get
LOG: could not recognize system timezone, defaulting to Etc/GMT-4
HINT: You can specify the correct timezone in postgresql.conf.
So what is your system timezone anyway (and
On Sun, May 23, 2004 at 04:58:29PM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
First I initdb'd without TZ set. So every time I start the server I get
LOG: could not recognize system timezone, defaulting to Etc/GMT-4
HINT: You can specify the correct timezone in
Alvaro Herrera [EMAIL PROTECTED] writes:
First I initdb'd without TZ set. So every time I start the server I get
LOG: could not recognize system timezone, defaulting to Etc/GMT-4
HINT: You can specify the correct timezone in postgresql.conf.
I've fixed the minor issue here, which is that
16 matches
Mail list logo