From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgadmin(at)pse-consulting(dot)de>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Timezone for %t log_line_prefix |
Date: | 2004-08-05 02:41:04 |
Message-ID: | 3638.24.211.141.25.1091673664.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane said:
>
> Since we do have control over the timezone library now, one possible
> answer is to extend the src/timezone API so that it's possible to
> convert/format against more than a single timezone. We could then
> remember the zone setting inherited from the postmaster and always use
> that when formatting timestamps for the log, while not changing the
> behavior for operations at the SQL level.
>
> However, this is probably a bit more work than is reasonable to
> undertake right now, when we're already overdue for beta. For the
> moment I'm really thinking that we ought to just #ifdef out the %Z on
> Windows, and plan to do something nicer in 8.1.
>
I think this counts as a bug, but I don't see that it needs to hold up the
beta release - I am assuming we expect several betas before we go gold.
Could it be fixed nicely in the next week or so?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-05 02:47:00 | Re: DROP TABLESPACE causes panic during recovery |
Previous Message | Tom Lane | 2004-08-05 02:25:48 | Re: Timezone for %t log_line_prefix |