Re: ISN was: Core Extensions relocation
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Geoghegan <peter@2ndquadrant.com>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2011-11-17T17:50:01Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Updates to contrib/isn ISBN tables.
- 6d1af7b21807 9.1.0 cited
-
Add a "LIKE = typename" clause to CREATE TYPE for base types. This allows
- 3f936aacc057 8.4.0 cited
Robert Haas <robertmhaas@gmail.com> writes: > At the same time, I still think we should push this out to PGXN or > pgfoundry or something. The fact that it's useful to some people does > not mean that it's a good example for other people to follow, or that > we want the core distribution to be in the process of tracking ISBN > prefixes on behalf of PostgreSQL users everywhere. I wouldn't object to that as long as we replaced it with some other module that had a similar relationship to core types. We'd never have realized the need for CREATE TYPE's LIKE option, until it was far too late, if we'd not had contrib/isn to show up the problem (cf commit 3f936aacc057e4b391ab953fea2ffb689a12a8bc). But really I think this discussion is making a mountain out of a molehill. If tracking ISBN prefix changes is such a time-consuming activity, why have we not seen a steady stream of update patches from users? By my count there's been just one such patch since 2006 (commit 6d1af7b2180719102a907bd3e35d218b43e76ad1). regards, tom lane