pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@heroku.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: RFC: Remove contrib entirely
Date: Fri, 29 May 2015 15:08:27 -0700
Message-ID: <5568E35B.6060109@agliodbs.com> (raw)
In-Reply-To: <WM!e93de1c7379c4d9114f1afb382222c222410848371ea9d5d2c613e828e6938af7d45ab06d95663fc2ed79c5e9ab2c90d!@asav-1.01.com>
References: <55674016.80005@commandprompt.com>
	<CAFj8pRC=sccsmdTTVT0XW316-HACK0Fkh8PYAOwVaGSANV80AA@mail.gmail.com>
	<CAECtzeUk_e=uCrwJSz-Z5MbiaqwuFf2gCs9iVkV8LTMesXAZ7Q@mail.gmail.com>
	<CAB7nPqREqu33nQZOnqP-U4F_b643vNZLa24YQ7G8DtEiJ=6U_g@mail.gmail.com>
	<CAFj8pRCAZDQs_ObBb46yfxS-t4rmnC-ujYD2nTCx7jRb2GENGA@mail.gmail.com>
	<WM!cba09fcb04a200dca6aa50578870e5360aceff298c70e35b89e1c83bb825513e3e16610e8589312b97b9deb3c9c52b72!@asav-1.01.com>
	<5568B43E.5030003@agliodbs.com>
	<CAM3SWZR_5+BZ0bfYas0aFqzKtMOzwgeVxLFcoADdzVHk8C_YgA@mail.gmail.com>
	<WM!55dc4215d3d71da9dd4a8bb3007479f41afcd00bae64bf4ffb96f86b4a135d0f1609c2953c807533ab1bef7ce257301b!@asav-2.01.com>
	<5568D5A4.3020002@agliodbs.com>
	<4946.1432935300@sss.pgh.pa.us>
	<CAM3SWZQox9UOPPF6wr25ZY8g91+EN9TbdB=EOdj6JNAchXaz-A@mail.gmail.com>
	<5372.1432936491@sss.pgh.pa.us>
	<WM!e93de1c7379c4d9114f1afb382222c222410848371ea9d5d2c613e828e6938af7d45ab06d95663fc2ed79c5e9ab2c90d!@asav-1.01.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 05/29/2015 02:54 PM, Tom Lane wrote:
> Peter Geoghegan <pg@heroku.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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (84+ messages)  latest in thread

Message-ID: <5568E35B.6060109@agliodbs.com>
Permalink:  ../5568E35B.6060109@agliodbs.com/
Also on:    postgresql.org/message-id/5568E35B.6060109@agliodbs.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us, pg@heroku.com
  Subject: Re: RFC: Remove contrib entirely
  In-Reply-To: <5568E35B.6060109@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox