From: | Jeff Davis <jdavis-pgsql(at)empires(dot)org> |
---|---|
To: | nd02tsk(at)student(dot)hig(dot)se |
Cc: | PgSQL General List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: The reasoning behind having several features outside |
Date: | 2004-10-25 19:45:19 |
Message-ID: | 1098733519.6589.18.camel@jeff |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Other people have answered, but I'd like to add:
It makes it much faster to fix bugs and improve features in the projects
outside of the source tree. If replication has a bug, you don't want to
wait for the next point release, you want a fix *now*. PostgreSQL is a
big project, and can't make new point releases every time a bug appears
in a small subsystem.
To make an analogy, imagine if you had to wait for a new release of your
operating system to fix a bug in an SSL library?
Regards,
Jeff Davis
On Mon, 2004-10-25 at 20:19 +0200, nd02tsk(at)student(dot)hig(dot)se wrote:
> Hello
>
> Why is it that PostgreSQL chooses to have features like replication,
> fulltext indexing and GIS maintained by others outside of the sourcetree?
>
> I appreciate any answers.
>
> Thank you.
>
> Tim
>
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
--
Jeff Davis <jdavis-pgsql(at)empires(dot)org>
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2004-10-25 19:45:40 | Re: PgSQL MVCC vs MySQL InnoDB |
Previous Message | Franco Bruno Borghesi | 2004-10-25 19:33:33 | Re: ON DELETE trigger blocks delete from my table |