Django threw a cryptic "dictionary update sequence" error—but the real culprit was a forgotten `name=` parameter in a URL configuration.

PostgreSQL's query planner guesses exactly 200 distinct values when it lacks statistics on a parent partitioned table, leading to wildly inaccurate cost…

Django's "Site matching query does not exist" error usually means you forgot to create a site record or set SITE_ID in settings—here's how to fix it.

Composite indexes on (A, B, C) can't help queries on just (B)? That's not technically true, but it's still good advice.

Monitor PostgreSQL replication lag with a simple timestamp table and cron job. This cheerful approach beats complex WAL math for many setups.

Talk slides from PGConf EU 2016 on securing PostgreSQL are now available. Learn practical strategies for hardening your database against common threats.

The slides from "Unclogging the VACUUM" presentation at PGConf EU 2016 are now online. Learn how to keep PostgreSQL's cleanup process running smoothly.

Mastering PostgreSQL across operations, compliance, and Python ecosystems: four talks on making Postgres work beyond the DBA role.

Stop mixing postgresql.conf edits between the middle and the end of the file.

More indexes don't always mean faster queries. Adding eight indexes to a test table slowed inserts by 14×, turning a 2-minute operation into 27 minutes.