After far too long, blog’s conversion to PostgreSQL and Django complete.

A viral Medium article claims PostgreSQL 18 is revolutionary with ten incredible new features.

Exposing PostgreSQL port 5432 to the public Internet invites brute-force attacks, DoS vulnerabilities, and potential data corruption.

PostgreSQL 12's INDEX_CLEANUP option can tank your query performance if misused. Learn when you absolutely need it, and why you almost certainly don't.

Stale .pyc files from deleted Python modules can cause mysterious bugs in production. Always clean them out during deploys.

Pick your PostgreSQL locale wisely: C.UTF-8 for speed, ICU for multilingual accuracy, or POSIX if you're ASCII-only and desperate.

Comparing PostgreSQL collation methods reveals surprising performance gaps: ICU beats libc by 5x for language-specific sorts, while the built-in C.UTF8…

When locale libraries change beneath your database, indexes silently break. Learn why this happens and how PostgreSQL now warns you.

PostgreSQL offers three locale providers—libc, ICU, and the new builtin provider—each with different trade-offs for character collation and localization.

Use UTF-8 for your PostgreSQL database. We explain why it's the right choice and when the performance argument for C encoding actually fails you.