This is a discussion on Re: ARC patent within the pgsql Hackers forums, part of the PostgreSQL category; --> Andrew Dunstan <andrew@dunslane.net> writes: > Simon Riggs wrote: > >>So, it also seems clear that 8.0.x should eventually have ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Andrew Dunstan <andrew@dunslane.net> writes: > Simon Riggs wrote: > >>So, it also seems clear that 8.0.x should eventually have a straight >>upgrade path to a replacement, assuming the patent is granted. We >>should therefore plan to: 1. improve/replace ARC for 8.1 2. backport >>any replacement directly onto 8.0STABLE as soon as any patent is >>granted > > One of the reasons for Postgres' well deserved reputation for > stability and reliability is that stable branches are > ... stable. Backporting a large item like cache replacement mechanism > doesn't seem to fit that too well. I wouldn't want to do that except > as a complete last resort. Exactly, which is why it probably won't happen. Tom's got the right idea. Simply release 8.0, and then start planning for 8.1. If and when IBM gets this patent approved, and if and when IBM starts sending out letters then PostgreSQL will be prepared with non-infringing versions. The *real* moral of the story, however, is that it is not smart for developers to go poking through patent databases. The real problems with patents begin when the patent holder can prove that you *knew* about an *approved* patent and still released the software anyhow. So don't browse through the patent databases, and for heaven's sake, if you find a patent that PostgreSQL *might* be infringing whatever you do don't post about it on the PostgreSQL mailing lists. I am not a lawyer, but I think that the only sane thing to do is to follow the lead of the Linux kernel developers and stay away from any sort of patent research. You really don't want to know how many patents PostgreSQL is infringing, and you certainly don't want to talk about it on a public forum (or anywhere else). My guess is that IBM isn't likely to be interested in spending millions of dollars litigating agains the PostgreSQL project and various PostgreSQL end users. Suing customers (and potential customers) is always bad form, and chasing after a Free Software project is likely to be a PR disaster. However, even if IBM were interested in "cashing in" on this patent, they can't do that until the patent is actually granted. Jason ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org |
| ||||
| Ühel kenal päeval (esmaspäev, 17. jaanuar 2005, 23:22+0000), kirjutas Simon Riggs: > On Mon, 2005-01-17 at 14:02 -0800, Joshua D. Drake wrote: > > >IBM can NEVER sue customers for using infringing > > >code before first informing them of infringement and > > >giving reasonable time to upgrade to uninfringing > > >version. .... > It seems clear that anybody on 8.0.0ARC after the patent had been > granted could potentially be liable to pay damages. At best, the > community would need to do a "product recall" to ensure patents were not > infringed. > > So, it also seems clear that 8.0.x should eventually have a straight > upgrade path to a replacement, assuming the patent is granted. > > We should therefore plan to: > 1. improve/replace ARC for 8.1 "improved" ARC still needs licence from IBM if they get the patent and our "improved" one infringes any claims in it. Actually getting patents on all useful improvements on existing patent has been a known winning strategy in corporate patent hardball - you force the original patent holder to negotiate, as he's rendered unable to improve his design without infringing your patents. IIRC some early electronic consumer devices were wrangled out of single company control that way. We could consider donating our improvements to some free patent foundation to be patented for this kind of action plan. -- Hannu Krosing <hannu@tm.ee> ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings |