ISBN range table

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: ISBN range table
Date: 2026-04-12 11:37:19
Message-ID: CA+hUKG+-2=tq15fLm=MbJhCTA=i-XJ=ZDMWjiWUg_eGH9cfP2Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

A recent-ish thread[1] made me wonder what that big table of data
does, and why we have a random update every decade or so, and I came
up with the attached.

It's pretty low stakes stuff: it controls where hyphens are inserted.
This happens when new ranges are carved out for publishers, so to pick
an example ISBN plucked from Wikipedia[2], here's an ISBN that is
shown differently after the attached:

postgres=# select '9791186178140'::isbn;
isbn
-----------------
979-118617814-0
(1 row)

postgres=# select '9791186178140'::isbn;
isbn
-------------------
979-11-86178-14-0

[1] https://www.postgresql.org/message-id/flat/e0a62134-83da-4ba4-8cdb-ceb0111c95ce(at)eisentraut(dot)org
[2] https://en.wikipedia.org/wiki/List_of_ISBN_registration_groups

Attachment Content-Type Size
0001-contrib-isb-Update-ISBN.h-automatically.patch text/x-patch 60.0 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-04-12 11:47:10 Re: Non-compliant SASLprep implementation for ASCII characters
Previous Message Bertrand Drouvot 2026-04-12 10:49:38 Use stack allocated StringInfoDatas, where possible (round 2)