From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Timezone for %t log_line_prefix |
Date: | 2004-08-04 21:08:11 |
Message-ID: | 10612.1091653691@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Andreas Pflug wrote:
>> If %t is used in log_line_prefix, win32's strftime will print a very
>> long timezone information, e.g. "W. Europe Daylight Time" where Linux
>> would write "UTC". This makes the timestamp consuming more than half
>> of an average line length.
>> Do we have alternatives to the long form? Do we need the timezone
>> information at all? We know already it's the server's time. Another
>> alternative would be a short timestamp (%t vs. %T) to have both.
> That's ugly, and unfortunately %z is GNU-specific.
Does Windows' strftime have any short zone name %-spec? Seems like a
quick #ifdef WIN32 to use a more compact zone name would be the best
solution.
I'd be inclined to leave out the zone field *on Windows only* if there
is no %-spec that uses something more reasonable. I don't think this
problem justifies adding more %-options to log_line_prefix.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-08-04 21:13:51 | Re: PITR - recovery to a particular transaction |
Previous Message | Tom Lane | 2004-08-04 20:54:26 | Re: More ALTER TABLE/TYPE bugs |