| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Joshua Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ISN was: Core Extensions relocation |
| Date: | 2011-11-16 01:49:17 |
| Message-ID: | CAEYLb_UDWOc-Ax3q_s+N6LFZsNiPxWpaQZX14kOennOrg9bavw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16 November 2011 01:09, Joshua Berkus <josh(at)agliodbs(dot)com> wrote:
> People are already using ISN (or at least ISBN) in production. It's been around for 12 years.
contrib/isn has been around since 2006. The argument "some unknowable
number of people are using this feature in production" could equally
well apply to anything that we might consider deprecating.
I am not arguing for putting isn on PGXN. I'm arguing for actively
warning people against using it, because it is harmful. Any serious
use of the ISBN datatypes can be expected to break unpredictably one
day, and the only thing that someone can do in that situation is to
write their own patch to contrib/isn. They'd then have to wait for
that patch to be accepted if they didn't want to fork, which is a very
bad situation indeed. This already happened once.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Royce Ausburn | 2011-11-16 03:02:05 | Re: [PATCH] Unremovable tuple monitoring |
| Previous Message | Robert Haas | 2011-11-16 01:26:11 | Re: [PATCH] Unremovable tuple monitoring |