Sirius Blog: You ask, we answer!
Originally published back in October 2012, this classic article series is undergoing a facelift and update!
We often get asked about PostgreSQL, and especially how it compares with proprietary enterprise-class Databases like Oracle or MS-SQL. In this classic series, revised and updated for today's PostgreSQL, we get right under the hood and explain, in plain English, just how the world's greatest Open Source Database works... You ask, we answer!
One of the first questions potential Open Source customers want to know when they start the research process is How much does Open Source (support/consultancy/training/systems integration) cost? Here at SiriUS, I'd imagine we get this question hundreds and hundreds of times a year, usually within the first few minutes of the first conversation.
Here at Sirius we hear a lot from our customers and prospective customers about the kinds of problems they have with Linux and especially Linux Support.
These are a few of them:
In Part 1 we looked at how PostgreSQL handles data concurrency, MVCC, and learned that understanding MVCC is critical for understanding PostgreSQL. Part 2 continued with MVCC and focused on concurrent access.
In the first two articles we examined vacuums, clusters and freeze. In this third and final piece we look at indexes and backups.
What are indexes and backups?
An index, like in a book, is a separate set of information that tells us what is where and saves having to re-read the whole book to find something. PostgreSQL uses indexes for a similar reason and broadly in a similar way.