Re: ISN was: Core Extensions relocation

All,

> I agree.  The argument that this code is useful as example code has
> been offered before, but the justification is pretty thin when the
> example code is an example of a horrible design that no one should
> ever copy.

People are already using ISN (or at least ISBN) in production.  It's been around for 12 years.  So any step we take
withcontrib/ISN needs to take that into account -- just as we have with Tsearch2 and XML2.
 

One can certainly argue that some of the stuff in /contrib would be better on PGXN.  But in that case, it's not limited
toISN; there are several modules of insufficient quality (including intarray and ltree) or legacy nature which ought to
bepushed out.  Probably most of them.
 

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
San Francisco