| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFC: Remove contrib entirely |
| Date: | 2015-05-29 21:54:51 |
| Message-ID: | 5372.1432936491@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-05-29 22:02:36 | Re: [CORE] postpone next week's release |
| Previous Message | Peter Geoghegan | 2015-05-29 21:51:42 | Re: RFC: Remove contrib entirely |