Re: [GENERAL] The reasoning behind having several features outside

2004-10-30 Thread Alvaro Herrera
On Sat, Oct 30, 2004 at 04:39:42PM -0300, Marc G. Fournier wrote: > On Sat, 30 Oct 2004, Joshua D. Drake wrote: > > >No, not really. Because items such as plPerl don't require > >changes to the backend. Replication requires changes to the backend. > > Replication doesn't require changes to the ba

Re: [GENERAL] The reasoning behind having several features outside

2004-10-30 Thread Tom Lane
"Marc G. Fournier" <[EMAIL PROTECTED]> writes: > On Sat, 30 Oct 2004 [EMAIL PROTECTED] wrote: >> 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

Re: [GENERAL] The reasoning behind having several features outside

2004-10-30 Thread Jan Wieck
On 10/30/2004 3:39 PM, Marc G. Fournier wrote: On Sat, 30 Oct 2004, Joshua D. Drake wrote: 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? No, not r

Re: [GENERAL] The reasoning behind having several features outside

2004-10-30 Thread Marc G. Fournier
On Sat, 30 Oct 2004, Joshua D. Drake wrote: 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? No, not really. Because items such as plPerl don't requi

Re: [GENERAL] The reasoning behind having several features outside

2004-10-30 Thread Joshua D. Drake
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? No, not really. Because items such as plPerl don't require changes to the backend. Replication re

Re: [GENERAL] The reasoning behind having several features outside

2004-10-30 Thread Marc G. Fournier
On Sat, 30 Oct 2004 [EMAIL PROTECTED] 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

Re: [GENERAL] The reasoning behind having several features outside

2004-10-30 Thread nd02tsk
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

Re: [GENERAL] The reasoning behind having several features outside of source?

2004-10-29 Thread Chris Browne
[EMAIL PROTECTED] writes: > 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. Part of the answer is that "there are many answers." As Jan Wieck will mention, there are mult

Re: [GENERAL] The reasoning behind having several features outside

2004-10-25 Thread Jeff Davis
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 p

Re: [GENERAL] The reasoning behind having several features outside of source?

2004-10-25 Thread Andrew Sullivan
On Mon, Oct 25, 2004 at 08:19:20PM +0200, [EMAIL PROTECTED] 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 can tell you for sure that the replication systems are aimed at differe

Re: [GENERAL] The reasoning behind having several features outside

2004-10-25 Thread Marc G. Fournier
On Mon, 25 Oct 2004 [EMAIL PROTECTED] wrote: Hello Why is it that PostgreSQL chooses to have features like replication, fulltext indexing and GIS maintained by others outside of the sourcetree? well, in the case of replication, there are about a half dozen replication solutions currently out there

Re: [GENERAL] The reasoning behind having several features outside of source?

2004-10-25 Thread Lamar Owen
On Monday 25 October 2004 14:19, [EMAIL PROTECTED] wrote: > Why is it that PostgreSQL chooses to have features like replication, > fulltext indexing and GIS maintained by others outside of the sourcetree? I'll make the attempt to answer best I can. PostgreSQL's architecture is very open and highl

Re: [GENERAL] The reasoning behind having several features outside

2004-10-25 Thread Jan Wieck
On 10/25/2004 2:19 PM, [EMAIL PROTECTED] wrote: Hello Why is it that PostgreSQL chooses to have features like replication, fulltext indexing and GIS maintained by others outside of the sourcetree? Because those are very diverse features. Replication especially, which is a bunch of different techni

Re: [GENERAL] The reasoning behind having several features outside

2004-10-25 Thread Joshua D. Drake
[EMAIL PROTECTED] wrote: Hello Why is it that PostgreSQL chooses to have features like replication, Well this is because there are multiple versions of replication and each has pros and cons. The community does not wish to endorse any of them. fulltext indexing and GIS maintained by others outsid

[GENERAL] The reasoning behind having several features outside of source?

2004-10-25 Thread nd02tsk
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 o