Re: Do we really want to migrate plproxy and citext into PG core distribution? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Do we really want to migrate plproxy and citext into PG core distribution?
Date
Msg-id 4948.1216762608@sss.pgh.pa.us
Whole thread Raw
In response to Re: Do we really want to migrate plproxy and citext into PG core distribution?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Do we really want to migrate plproxy and citext into PG core distribution?  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> Tom, Simon, etc.:
> Of the several things which "PostgreSQL could learn from MySQL" which we 
> covered at pgCon was that the requirement to hunt hither and yon for 
> popular add-ins is one of the primary reasons for developers not using 
> PostgreSQL.

Agreed, but I think the best response to that is something CPAN-like
for people to easily get hold of recognized extensions, and next best
(or also) a "kitchen sink" installer package that agglomerates the core
and selected outside projects.  There aren't any successful extensible
projects that ignore their own extensibility and put everything
interesting into the core project.

> The general case aside, I really feel strongly that citext belongs in 
> core unless we come up with some other means to do case-insensitive 
> text. It's one of the top 10 newbie questions.

Maybe.  I'd be happier about it if I could see a reasonable upgrade path
from that to a SQL-spec-compliant solution (ie, something collation
based).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Markus Wanner
Date:
Subject: Re: Transaction-controlled robustness for replication
Next
From: Markus Wanner
Date:
Subject: Re: Postgres-R: tuple serialization