Re: Units for storage of internal time zone offsets

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Units for storage of internal time zone offsets
Date: 2002-07-09 15:10:11
Message-ID: 3D2AFCD3.9B6AEFEB@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Is there a reason for the restriction to one byte? Offhand I don't
> recall that we store TZ offsets on disk at all...

Ah, we don't. Sorry I wasn't clear. This is only for the lookup table we
use to interpret time zones on *input*. It is contained in
src/backend/utils/adt/datetime.c

And it has no long-term ramifications; it is entirely self-contained and
does not result in information being stored on disk.

This table does not have any concept of multiple values for a particular
string time zone (e.g. "PST" or "EDT"). If/when we incorporate the zic
stuff we will still need this lookup table, unless we develop an API to
allow finding these within the zic database.

- Thomas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-07-09 15:18:14 Re: Units for storage of internal time zone offsets
Previous Message Lamar Owen 2002-07-09 15:04:15 Re: (A) native Windows port