https://postgres.ai/blog2026-11-05T12:00:00.000Zhttps://github.com/jpmonette/feedhttps://postgres.ai/favicon.svgPostgresAI<![CDATA[UUIDv4 vs UUIDv7: what a random primary key costs in Postgres]]>https://postgres.ai/blog/20261105-uuidv4-vs-uuidv72026-11-05T12:00:00.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[What your Postgres is waiting for, and why the dashboard can't tell you]]>https://postgres.ai/blog/20261103-what-postgres-is-waiting-for2026-11-03T12:00:00.000ZDmitry Fomindmitry@postgres.ai<![CDATA[Dump/restore done. Now what?]]>https://postgres.ai/blog/20261028-dump-restore-now-what2026-10-28T12:00:00.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[DBLab 4.2: clone upgrades, simplified install, retention, and more]]>https://postgres.ai/blog/20260917-dblab-engine-4-2-released2026-09-17T00:00:00.000ZDenis Morozovdenis@postgres.ai<![CDATA[DBLab 4.1: protection leases, Teleport, Prometheus, and more]]>https://postgres.ai/blog/20260408-dblab-engine-4-1-released2026-04-08T00:00:00.000ZDenis Morozovdenis@postgres.ai<![CDATA[PG18 preserves planner statistics on upgrade — even from PG14]]>https://postgres.ai/blog/20260324-pg18-stats-upgrade-across-versions2026-03-24T12:00:00.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[How moving one word can speed up a query 10–50x]]>https://postgres.ai/blog/20260311-not-exists-vs-exists-partial-index2026-03-11T12:00:00.000ZMaxim Bogukhttps://www.linkedin.com/in/maxim-boguk-b1bb9980/Nikolay Samokhvalovnik@postgres.ai<![CDATA[The hidden cost of invalid indexes in Postgres (yes, even on Supabase/RDS/Neon)]]>https://postgres.ai/blog/20260106-invalid-index-overhead2026-01-06T01:23:45.000ZDmitry Fomindmitry@postgres.ai<![CDATA[#PostgresMarathon 2-013: Why keep your index set lean]]>https://postgres.ai/blog/20251110-postgres-marathon-2-013-why-keep-your-index-set-lean2025-11-10T23:59:59.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[#PostgresMarathon 2-012: Ultra-fast replica creation with pgBackRest]]>https://postgres.ai/blog/20251105-postgres-marathon-2-012-ultra-fast-replica-creation-pgbackrest2025-11-05T23:59:59.000ZNikolay Samokhvalovnik@postgres.aiMaxim Bogukhttps://www.linkedin.com/in/maxim-boguk-b1bb9980/<![CDATA[#PostgresMarathon 2-011: Prepared statements and partitioned tables — the paradox, part 3]]>https://postgres.ai/blog/20251030-postgres-marathon-2-0112025-10-30T23:59:59.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[#PostgresMarathon 2-010: Prepared statements and partitioned table lock explosion, part 2]]>https://postgres.ai/blog/20251029-postgres-marathon-2-0102025-10-29T23:59:59.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[#PostgresMarathon 2-009: Prepared statements and partitioned table lock explosion, part 1]]>https://postgres.ai/blog/20251028-postgres-marathon-2-0092025-10-28T12:00:00.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[#PostgresMarathon 2-008: LWLock:LockManager and prepared statements]]>https://postgres.ai/blog/20251014-postgres-marathon-2-0082025-10-14T23:59:59.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[#PostgresMarathon 2-007: Should we worry about pg_blocking_pids()'s observer effect?]]>https://postgres.ai/blog/20251013-postgres-marathon-2-0072025-10-13T00:00:00.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[#PostgresMarathon 2-006: Mysterious max_locks_per_transaction]]>https://postgres.ai/blog/20251010-postgres-marathon-2-0062025-10-10T00:00:00.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[#PostgresMarathon 2-005: More LWLock:LockManager benchmarks for Postgres 18]]>https://postgres.ai/blog/20251009-postgres-marathon-2-0052025-10-09T00:00:00.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[#PostgresMarathon 2-004: Fast-path locking explained]]>https://postgres.ai/blog/20251008-postgres-marathon-2-0042025-10-08T00:00:00.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[#PostgresMarathon 2-003: The roots of LWLock:LockManager]]>https://postgres.ai/blog/20251007-postgres-marathon-2-0032025-10-07T00:00:00.000ZNikolay Samokhvalovnik@postgres.ai<![CDATA[#PostgresMarathon 2-002: Relation-level locks]]>https://postgres.ai/blog/20251005-postgres-marathon-2-0022025-10-06T00:00:00.000ZNikolay Samokhvalovnik@postgres.ai