| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: storing TZ along timestamps |
| Date: | 2011-05-27 21:39:53 |
| Message-ID: | E769A699-25EB-4822-9127-634E791B0B6E@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 27, 2011, at 2:35 PM, Tom Lane wrote:
> "David E. Wheeler" <david(at)kineticode(dot)com> writes:
>> I like it, but what do you do when a TZ has been renamed or has ceased
>> to exist.
>
> As far as that goes, I think "nothing" is a sufficient answer. There's
> no requirement that an OID in the mapping table correspond to a live TZ.
> It's just a more compact way of storing a string name.
Well then you'd just want to be sure to never delete TZs.
I think the issue of trying this week to use a TZ that was removed last week might be more problematic. I mean, we could just let the user use it, but that hardly seems wise…
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2011-05-27 21:48:06 | Re: minor patch submission: CREATE CAST ... AS EXPLICIT |
| Previous Message | Tom Lane | 2011-05-27 21:35:41 | Re: storing TZ along timestamps |