>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.
Time permitting, I was planning to address this in 8.1. (well, 7.6 then,
but I guess it's 8.1 now). Not specificalyl the issue, but the
groundwork API change to make it possible.
>However, this is probably a bit more work than is reasonable to
>undertake right now, when we're already overdue for beta.
Definitly.
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
