Re: The reasoning behind having several features outside

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: nd02tsk(at)student(dot)hig(dot)se
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: The reasoning behind having several features outside
Date: 2004-10-30 19:15:44
Message-ID: 20041030161330.C6085@ganymede.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, 30 Oct 2004 nd02tsk(at)student(dot)hig(dot)se wrote:

> Jeff Davis wrote:
>
>> 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.
>
> Replication is one subsystem not included in source tree. But PostgreSQL
> has other subsystems that are included such as plugins for procedural
> languages. So isn't the same risks involved with them?

Yes, which is why you will find that several of them are 'outside
projects' for development purposes ... in fact, if you looked back at the
earlier 7.x series, you will find that they had more interfaces then the
current code does ... alot has been moved out over the years. libpq++ is
a prime example of something that had official status for the longest
time, but where someone came along and wrote a 'better' version of it,
which is now on gborg ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Marc G. Fournier 2004-10-30 19:39:42 Re: The reasoning behind having several features outside
Previous Message Joshua D. Drake 2004-10-30 19:15:18 Re: The reasoning behind having several features outside