Re: storing TZ along timestamps

On Jul 25, 2011, at 6:22 PM, Robert Haas wrote:
> On Mon, Jul 25, 2011 at 6:26 PM, Jim Nasby <jim@nasby.net> wrote:
>> Hrm, don't we only pull in ZIC info on a reload? Or do we actually refer to it dynamically all the time? Perhaps we
canenforce that we'll only recognize new TZ info as part of a config reload? 
>
> Hmm.  That might work in theory, but I don't see any good way to
> update every database's tz table on each reload.

I'm assuming that the issue here is that multiple backends could be connected to the same database, and we don't want
allof them to try to actually do the updates, only the first one that discovers the change. If that's the problem you
foreseethen perhaps it's a non-issue... if each backend only updates things that have actually changed, and they do
thatwith race-free 'merge' logic, then only the first backend to attempt the update would end up finding actual work to
do.

Or are you seeing a problem I'm missing?
--
Jim C. Nasby, Database Architect                   jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net