From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
Cc: | David Fetter <david(at)fetter(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: A renewed plea for inclusion of zone.tab |
Date: | 2009-04-10 21:35:07 |
Message-ID: | 1662.1239399307@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> On Apr 10, 2009, at 12:15 PM, Tom Lane wrote:
>> I gave my reasoning before: widening this API has possibly nontrivial
>> future maintenance costs, and the actual use-case for the data is
>> unconvincing.
> It seems to me that the immediate patch to simply copy zone.tab has no
> effect on the API. That's a debate worth having, but I don't think
> it's relevant to this particular patch, is it?
Well, as far as I can see the immediate patch is pretty useless without
an API change in front of it. Andrew was threatening to write a
pgfoundry module that read from the file directly, but considering that
such a thing would require superuser privileges it doesn't seem like a
particularly attractive answer.
The immediate patch has other bogosities too: why not iso3166.tab too,
if we are going to start exposing this data? Without an agreed-on API
change we don't really know what we need or why.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-04-10 21:54:25 | Unicode string literals versus the world |
Previous Message | Andrew Dunstan | 2009-04-10 21:33:50 | Re: pg_restore dependencies |