Re: why is postgres-R not in standard dev Path. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: why is postgres-R not in standard dev Path.
Date
Msg-id 28620.1090940626@sss.pgh.pa.us
Whole thread Raw
In response to why is postgres-R not in standard dev Path.  (chinni <naveen.bysani@gmail.com>)
List pgsql-hackers
chinni <naveen.bysani@gmail.com> writes:
> Did you guys debate on merging it.

Yes.

If it were actually synced with our current CVS and potentially
mergeable, the debate might have been longer :-(.  But in point of fact,
postgres-R has never been less than two releases behind in the past five
years, and so there was never a time when merging it was technically
feasible.

There are also political issues --- merging it into our core would be
seen as blessing one particular replication solution to the exclusion
of others.

And last I checked, there were licensing issues, because postgres-R
depends on a group-communication package that doesn't use a BSD-style
license.

I'd personally be willing to override the political objections if the
other two categories of problems were surmounted.  But I doubt they
ever will be.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Savepoints inside functions
Next
From: Tom Lane
Date:
Subject: Re: Savepoints inside functions