Re: BUG #7903: EAN13s are shown ISBN values

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>
Cc: kurt(at)roeckx(dot)be, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7903: EAN13s are shown ISBN values
Date: 2013-02-26 21:45:19
Message-ID: 512D2CEF.9010209@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2/23/13 2:10 PM, Peter Geoghegan wrote:
> But then, contrib/isn also sanitises both ISBN
> ranges and EAN country codes using its own internal database, which
> ought to be kept in lockstep with an external database whose
> maintenance is highly decentralised - regional authorities make
> certain decisions that can create a need to update the database. I'm
> pretty sure that that database doesn't actually exist, at least all in
> one place, in the case of ISBN. So contrib/isn is fundamentally
> wrong-headed, and I would be quite happy to see its removal from
> contrib.

What's the alternative?

Have each user create their custom domain?

Is there a stable subset that we could maintain with minimal effort?

Would it be better if the module were removed from PostgreSQL core but
maintained externally where it can iterate faster and keep the database
up to date?

Is there a third-party library that does maintain such a database so
that this module could be based upon that instead of having to maintain
the database itself?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Frost 2013-02-26 22:16:53 Re: BUG #7902: lazy cleanup of extraneous WAL files can cause out of disk issues
Previous Message fburgess 2013-02-26 17:30:47 Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space.