Re: Proposal: replace no-overwrite with Berkeley DB

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: 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:02:19
Message-ID: 3.0.5.32.20000516100219.021cfd80@mail.rhyme.com.au
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.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: +61-03-5367 7422 | _________ \
Fax: +61-03-5367 7430 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-05-16 00:12:20 Insertion of index tuples are necessary ?
Previous Message Patrick Welche 2000-05-15 23:37:02 Re: reading row in backend