Legal documents = SCARY!!
That’s the typical equation, and it’s true – except when it comes to PostgreSQL.
Let me explain…
I have been told by both prospects and clients, that when they sit down to negotiate terms with Oracle, they are faced with more lawyers than they have engineers. No wonder one shudders at the thought of evaluating a database’s license.
If only all databases were as simple, legally, as PostgreSQL.
Can I use it? Yes!
Do I have to pay for using it? No!
Will I ever have to pay for using it? No!
But there is a limit on the amount of data I can store? No!
Then it must be limited in functionality? No!
You can modify it, you can embed it in your software, you can fork it, you can even distribute it freely – the license allows for all of that.
The PostgreSQL license is a grand total of 143 words. 143 ONLY! These words come together to tell you just 2 simple things:
- You can do whatever you want to do with the database
- You are not allowed to blame the University of California if you mess things up
Don’t believe me? Go ahead and read it yourself.
It won’t take more than 5 minutes – guaranteed!
Admittedly, that second point may seem like a turn-off for large enterprises that need someone to fall back on in case something goes wrong (a.k.a. a vendor). I think PostgreSQL has a leg up even in that area, but that’s going to be the topic of a subsequent blog…