Re: Proposal: replace no-overwrite with Berkeley DB

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Hannu Krosing <hannu(at)tm(dot)ee>, "Michael A(dot) Olson" <mao(at)sleepycat(dot)com>, pgsql-hackers(at)postgresql(dot)org, ned(at)greatbridge(dot)com
Subject: Re: Proposal: replace no-overwrite with Berkeley DB
Date: 2000-05-16 00:27:49
Message-ID: 200005160027.UAA26990@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-05-16 00:44:03 Re: reading row in backend
Previous Message Hiroshi Inoue 2000-05-16 00:12:20 Insertion of index tuples are necessary ?