Re: Proposal: replace no-overwrite with Berkeley DB - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Proposal: replace no-overwrite with Berkeley DB
Date
Msg-id 200005160027.UAA26990@candle.pha.pa.us
Whole thread Raw
In response to Re: Proposal: replace no-overwrite with Berkeley DB  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
> >
> >We could get perpetual rights to the code as integrated into our code. 
> >Also, if they change something, we could always take it as our own and
> >keep it working for us.  I think we would need something like that.
> >
> 
> One of the often-stated virtues of PGSQL is that it is easy for a company
> to take the source and go commercial. If you start integrating 'special
> license greements' into the development, then that advantage is severly
> reduced. 
> 
> A commercial operator has to form an agreement with sleepycat or rewrite
> the storage manager. Unless sleepycat grant a completely open license to
> PGSQL and all it's commercial descendants in perpetuity, it seems you may
> be removing one of the seeling points of PGSQL.

Yes, something like this would be required.

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: "Hiroshi Inoue"
Date:
Subject: Insertion of index tuples are necessary ?
Next
From: Tom Lane
Date:
Subject: Re: reading row in backend