| Product | PostgreSQL |
| Website | postgresql.org |
| Category | Database / Relational |
| License | PostgreSQL License (permissive, similar to MIT) |
| Pricing | Free and open source |
What Is PostgreSQL?
PostgreSQL is an advanced open-source relational database. It has been in development since 1986 and is known for correctness, standards compliance, extensibility, and a feature set that rivals commercial databases. PostgreSQL handles everything from a personal project to Instagram-scale workloads.
What makes PostgreSQL stand out is its balance. It’s relational but handles JSON documents natively. It’s ACID-compliant but fast. It’s standards-compliant but extensible. PostgreSQL doesn’t make you choose between correctness and flexibility — it gives you both.
Key Features
JSONB
Store and query JSON documents natively with JSONB. PostgreSQL indexes JSONB fields, supports JSON path queries, and lets you combine relational and document data in the same database. Need a relational schema for most of your data and a flexible document for metadata? PostgreSQL handles both.
Extensions
PostgreSQL’s extension system is unmatched. PostGIS adds geospatial queries. pgvector adds vector similarity search for AI/ML embeddings. TimescaleDB adds time-series optimization. pg_trgm adds fuzzy text search. Extensions extend PostgreSQL without forking it.
MVCC and Concurrency
Multi-Version Concurrency Control (MVCC) means readers never block writers and writers never block readers. Concurrent transactions see consistent snapshots without locking. This is why PostgreSQL handles high-concurrency workloads well.
Full-Text Search
Built-in full-text search with ranking, stemming, and language support. For many applications, PostgreSQL’s full-text search eliminates the need for a separate Elasticsearch cluster. GIN indexes make it fast.
Who Is This For?
- Any application that needs a reliable, feature-rich database
- Projects with relational data (users, orders, products, relationships)
- AI/ML applications (pgvector for embeddings)
- Geospatial applications (PostGIS)
Pros
- Most advanced open-source relational database
- JSONB for document-style data
- Extension ecosystem (PostGIS, pgvector, TimescaleDB)
- Truly open source (permissive license)
- Excellent concurrency (MVCC)
- Built-in full-text search
Cons
- Vertical scaling only (no native sharding)
- VACUUM overhead (MVCC trade-off)
- Configuration tuning needed for production
- Replication setup is more complex than MySQL
- Write-heavy workloads need careful tuning
Verdict
PostgreSQL is the default database choice. Unless you have a specific reason to choose something else (document-shaped data that truly doesn’t fit relations, or a managed NoSQL service you’ve already committed to), start with PostgreSQL. It handles relational data, JSON documents, full-text search, geospatial queries, and vector embeddings — all in one database.
The managed PostgreSQL landscape is excellent: Neon (serverless), Supabase (Firebase alternative built on Postgres), AWS RDS, Google Cloud SQL, and many others. You get PostgreSQL’s capabilities without the operational burden. For the vast majority of applications, PostgreSQL is the right choice.