Skip site navigation (1) Skip section navigation (2)

Re: Time zone definitions to config files

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org, David Fetter <david(at)fetter(dot)org>
Cc: joe(at)mcknight(dot)de, pgsql-patches(at)postgresql(dot)org
Subject: Re: Time zone definitions to config files
Date: 2006-07-26 02:37:20
Message-ID: 26584.1153881440@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
David Fetter <david(at)fetter(dot)org> writes:
> On Mon, Jul 24, 2006 at 11:59:34PM -0400, Tom Lane wrote:
>> The documentation is still in need of help ... in particular, Table
>> B-4 (timezone names) is now out of sync with reality.

> I'll take a whack at that patch this evening PDT or tomorrow evening
> at the latest.  We're too late in the cycle to go over this, but maybe
> we can figure out a way to have this data read from the same data
> source as the pg_timezones VIEW does at compile time.  Keeping two
> such table in synch seems error-prone.

Well, the problem is exactly that there is no "same data source"
anymore: the local DBA can customize the timezone list all he wants.

We could document what the out-of-the-box settings are, but is it
really useful to duplicate that info in the SGML docs?  We don't
for example provide a copy of psql \df+ output in the SGML docs,
and I'm wondering if this isn't kind of the same animal.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-07-26 03:05:08
Subject: Re: pgsql: /contrib/cube improvements: Update the calling convention for
Previous:From: Bruce MomjianDate: 2006-07-26 02:06:34
Subject: Re: [HACKERS] Resurrecting per-page cleaner for btree

pgsql-patches by date

Next:From: Tom LaneDate: 2006-07-26 03:05:08
Subject: Re: pgsql: /contrib/cube improvements: Update the calling convention for
Previous:From: Bruce MomjianDate: 2006-07-26 02:06:34
Subject: Re: [HACKERS] Resurrecting per-page cleaner for btree

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group