From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RFC: Remove contrib entirely |
Date: | 2015-05-29 22:08:27 |
Message-ID: | 5568E35B.6060109@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 05/29/2015 02:54 PM, Tom Lane wrote:
> Peter Geoghegan <pg(at)heroku(dot)com> writes:
>> The problem here is that these ranges are controlled by a
>> decentralized patchwork of national standards bodies, and the ranges
>> are always subject to revision. I think that it's egregious that
>> contrib/isn imagines it can track that with a static array.
>
> Well, that module has already been rewritten once (which proves that
> there's an audience out there for it). Perhaps somebody will rewrite it
> again to support a non-hardwired set of ranges. Now that we have the
> concept of an extension configuration table, that'd be one possible
> way to fix it ...
FWIW, neither of the projects I know of which uses ISBN has had any
issues with the range since the 2010 updates. While the ranges can be
updated in theory, in practice is happens glacially slowly.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2015-05-29 22:28:01 | Re: [CORE] postpone next week's release |
Previous Message | Peter Geoghegan | 2015-05-29 22:08:13 | Re: RFC: Remove contrib entirely |