Tag
19 articles tagged #PostgreSQL.
P.01Partitioning and sharding both split data up, and people mix up the terms constantly. Partitioning stays on one database and one server. Here's how range, list, and hash partitioning actually work, and when a partitioned table solves your problem before you need sharding at all.
P.02Read Committed, Repeatable Read, Serializable: most developers pick whatever their ORM defaults to and never ask why. Here's what each isolation level actually prevents, what it still allows, and how to pick one on purpose.
P.03A practical comparison of the four vector databases most teams actually shortlist for RAG and semantic search, with real pricing models, when each one wins, and the one question that should decide it for you.
P.04MySQL 9 shipped a native VECTOR column type and distance functions, no extension required. Here's how it actually compares to Postgres plus pgvector for real semantic search workloads, with working syntax for both.
P.05PostgreSQL 18 shipped in September 2025 and is now on its 18.4 point release. With PostgreSQL 19 still in beta, here's what 18's async I/O, UUIDv7, virtual generated columns, and OAuth support actually mean for a production upgrade decision today.
P.06PostgreSQL 19 Beta 1 shipped with a REPACK command that finally makes VACUUM FULL and CLUSTER safe to run without a maintenance window, plus parallel autovacuum and smarter async I/O. Here's what changed and what to test now.
P.07CVE-2026-12048 is a CVSS 9.3 stored XSS in pgAdmin 4 that lets a malicious PostgreSQL server inject JavaScript into your browser tab. Every version from 6.0 to 9.15 is affected. The fix is v9.16.
P.08Database engineer is distinct from data engineer. One designs schemas, tunes queries, and manages production Postgres. The other builds pipelines. Here's how to hire the one who keeps your app fast.
P.09Most slow queries come from a small set of fixable problems: missing indexes, N+1 patterns, and over-fetching. This is the practical diagnostic and fix guide.
P.10Row Level Security moves data isolation into the database where it belongs. Here's how to set it up for a multi-tenant SaaS, handle common edge cases, and avoid the traps that break it.
P.11The queries that destroy production Postgres databases share a small set of root causes. Here is how to find them, understand what EXPLAIN ANALYZE is telling you, and fix them without guessing.
P.12Neon separates storage from compute to make Postgres behave like a serverless resource. The branching feature is what actually changes the development workflow — here's how it works and when it's worth the migration.
P.13Connection exhaustion is one of the most common production failures for apps that scale. Here's how pooling works, which tool fits which setup, and the configuration decisions that matter.
P.14Add similarity search to your existing Postgres database using pgvector. Real setup, indexing strategies, and when you actually need a dedicated vector database.
P.15Every SaaS team eventually faces the multi-tenancy decision. The wrong choice creates migration pain later. Here's how to think through database-per-tenant, schema-per-tenant, and row-level security based on what your product actually needs.
P.16Running totals, rankings, moving averages, lag and lead comparisons: window functions handle the analytics queries that would otherwise require application-side loops or multiple round-trips. Here's how they work.
P.17ALTER TABLE locks your database. Your migration takes longer than expected. Users get errors. Here's how to handle schema changes that don't interrupt production traffic.
P.18Nearly 200 developers urged Oracle to rethink MySQL's future. We break down the open letter, the governance crisis, the rise of PostgreSQL and alternatives, and what developers should do next.
P.19The database landscape is consolidating around Postgres while SQLite finds new life at the edge. Meanwhile, vector databases have become essential infrastructure for AI applications.