Re: storing TZ along timestamps

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: storing TZ along timestamps
Date: 2011-05-27 21:09:02
Message-ID: 46BA08FD-6938-440B-9925-EBA049FEAD5B@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On May 27, 2011, at 1:43 PM, Alvaro Herrera wrote:

> Right now we rely on the tzdata files on disk for things like
> pg_timezone_names and other accesses of TZ data; so the files are the
> authoritative source of TZ info. So we need to ensure that whenever the
> files are updated, the catalogs are updated as well.
> I think we could make this work if we "refreshed" the catalog from the
> files on SIGHUP if the directory changes (say, a new timezone is
> created). Note that I am currently proposing to store only the zone
> names in the catalog, not the full TZ data.
>
> Are there objections to the general idea? If not, I'll flesh a more
> complete proposal.

I like it, but what do you do when a TZ has been renamed or has ceased to exist. Or, worse, existed last week, so last week's dates might still use it, but next week's must not?

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-05-27 21:10:42 Re: storing TZ along timestamps
Previous Message Alvaro Herrera 2011-05-27 21:02:25 Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch