PostgreSQL 8.0.2 released with patent fix

[Posted April 11, 2005 by corbet]

From:		"Marc G. Fournier" <scrappy-AT-postgresql.org>
To:		pgsql-announce-AT-postgresql.org
Subject:		[ANNOUNCE] PostgreSQL 8.0.2 Now Available
Date:		Sun, 10 Apr 2005 19:48:00 -0300 (ADT)
Cc:		pgsql-general-AT-postgresql.org


Over the past several weeks, Tom Lane has been working on replacing our 
old Cache Management Alorithm (ARC) with a new, patent free one (2Q).

In order to reduce the number of 8.x deployments out there that are using 
the old manager, we have just released 8.0.2, and encourage adminstrators 
to upgrade at their earliest convience.

For those already running 8.x on your production servers, please note that 
this upgrade does *NOT* require a dump restore, but due to a bump in the 
major version number for the client library (libpq), it *WILL* require all 
client applications to be recompiled at the same time.

For a full list of bugs fixed in this version, please see the HISTORY 
file, which can be found at:

 	http://www.postgresql.org/ftp/source/v8.0.2/HISTORY

With Source tarballs available at:

 	http://www.postgresql.org/ftp/source/v8.0.2

Binary/Install Packages for Windows are available at:

 	http://www.postgresql.org/ftp/binary/v8.0.2/win32/

And, for Bittorrent Users, David has put up the tar packages at:

 	http://bt.postgresql.org

Any bugs/problems with 8.0.2, please report them to:

 	pgsql-bugs@postgresql.org

Thank you ...


---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

(Log in to post comments)

PostgreSQL 8.0.2 released with patent fix

Posted Apr 11, 2005 22:46 UTC (Mon) by dlang (guest, #313) [Link]

frankly I think they made a mistake by not even asking IBM about the patent.

as commented on in the more detailed article it's unlikly that IBM would immediatly take legal action, especially as they were showing willingness to change it as nessasary.

so not postgres users are faced with the choice of getting a batch of fixes and loosing performance, or doing without the fixes. this is a bad position to put anyone in.

PostgreSQL 8.0.2 released with patent fix

Posted Apr 12, 2005 4:34 UTC (Tue) by jwb (guest, #15467) [Link]

Am I reading this incorrectly, or did they in fact break the wire protocol? If I move to 8.0.2, do I
need to recompile applications on totally unrelated machines? Or are they saying that I will need to
replace applications that run on the database server, due to the soversion increasing? if the latter,
why can't I just keep my old .so?

PostgreSQL 8.0.2 released with patent fix

Posted Apr 12, 2005 12:29 UTC (Tue) by nconway (guest, #3391) [Link]

The wire protocol did not change. All that happened is that the major version number of the libpq .so has been bumped. If you don't want to recompile any applications, just keep the 8.0.1 libpq around as well.

PostgreSQL 8.0.2 released with patent fix

Posted Apr 12, 2005 4:54 UTC (Tue) by Anonymous1 (guest, #29218) [Link]

Postgres uses a BSD License and IBM is unlikely to grant everyone free
use of its patent, so there wasn't a lot of point in asking IBM for
an exception.
This might have made sense for a GPL licensed project.

PostgreSQL 8.0.2 released with patent fix

Posted Apr 12, 2005 8:19 UTC (Tue) by khim (subscriber, #9252) [Link]

IBM is perfectly happy with BSD license. It will grant license for BSD-licensed software. Of course. "As published by OSI". Obviously.

That is: you'll get your license (with paper trail even!), but... you'll be unable to change terms of license later (and you'll be unable to make proprietary version of PostgreSQL).

FSF hacked copyright system to create copyleft. IBM hacked patent system to make non-copyleft open-source licenses copyleft as well. Pretty ingenious if you'll ask me.

Think about it: by granting big pile of patents for open source projects IBM makes "MySQL business model" possible for unrelated projects! If you are open-source developer - you can just forget about patents and hack freely: you have written license to do so. Once you'll try to make program proprietary... bam: you'll get letter with royalty demands pretty soon. Kinda defeats reason to license something under BSD license, but... Brilliant, just brilliant.

P.S. What I really do not get is why IBM waited for so long to make this move. I was sure they'll do something like this years ago, but I guess moment was wrong.

PostgreSQL 8.0.2 released with patent fix

Posted Apr 12, 2005 12:11 UTC (Tue) by Wol (subscriber, #4433) [Link]

As Khim said.

IBM is perfectly happy with a BSD licence.

Read IBM's patent pledge, and read it *CAREFULLY*. Provided the software *stays* BSD, the pledge continues to apply. But change the copyright licence, and you can lose the patent licence.

That said, I do understand this conflicts with the BSD principle that anyone should be free to use the code in any way they choose (including going proprietary). But can you blame IBM for not wanting people to use their own patents against them?

Cheers,
Wol

PostgreSQL 8.0.2 released with patent fix

Posted Apr 13, 2005 23:14 UTC (Wed) by alvherre (subscriber, #18730) [Link]

FYI, this LWN.net article and this comment have been quoted by ZDnet UK (including a link to the relevant PTO entry and Elein Mustain's article on the subject.)

PostgreSQL 8.0.2 released with patent fix

Posted Apr 12, 2005 12:05 UTC (Tue) by nconway (guest, #3391) [Link]

There were a few reasons why we didn't talk to IBM. We would have needed IBM to license the patent to PGDG (the open source project), as well as any commercial entity that wanted to modify and redistribute PostgreSQL. Since those commercial entities include companies like Fujitsu and Pervasive that compete with IBM, most people thought IBM wouldn't be willing to do this.

Also, there might have been more merit in talking to IBM if the patented algorithm could be shown to be significantly better than any unpatented alternative. However, all the tests we've run have indicated that 2Q has about the same performance as ARC -- if you have benchmarks that indicate otherwise, please post to the pgsql-hackers list about it. Going through a bunch of legal headaches for an algorithm that doesn't improve performance doesn't make a lot of sense. It's also worth noting that this entire subsystem has been rewritten in 8.1 for better locking performance -- because of the way the new locking scheme works, neither 2Q or ARC can be used, so the point is moot in the long run. That's why I think that a simple technical fix that doesn't hurt performance and doesn't involve lawyers makes the most sense.

Cheers,

Neil Conway