Add lockmanager tag to PostgresMarathon LWLock:LockManager posts

claude · claude · commit 7ec6bee40607 · 2026-05-11T23:26:42.000Z
diff --git a/blog/20251005-postgres-marathon-2-001.md b/blog/20251005-postgres-marathon-2-001.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-001: Lightweight and heavyweight locks"
 date: 2025-10-05
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager]
 ---
 
 To warm up, let's talk about lightweight and heavyweight locks (or "regular locks" or just "locks").
diff --git a/blog/20251005-postgres-marathon-2-002.md b/blog/20251005-postgres-marathon-2-002.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-002: Relation-level locks"
 date: 2025-10-06
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager]
 ---
 
 Let's talk about relation-level locks and various confusions, surprises and what is worth to remember in practice.
diff --git a/blog/20251007-postgres-marathon-2-003.md b/blog/20251007-postgres-marathon-2-003.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-003: The roots of LWLock:LockManager"
 date: 2025-10-07
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager]
 image: /assets/blog/20251007-postgres-marathon-2-003.png
 ---
 
diff --git a/blog/20251008-postgres-marathon-2-004.md b/blog/20251008-postgres-marathon-2-004.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-004: Fast-path locking explained"
 date: 2025-10-08
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager]
 image: /assets/blog/20251008-postgres-marathon-2-004-cover.png
 ---
 
diff --git a/blog/20251009-postgres-marathon-2-005.md b/blog/20251009-postgres-marathon-2-005.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-005: More LWLock:LockManager benchmarks for Postgres 18"
 date: 2025-10-09
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager]
 image: /assets/blog/20251009-postgres-marathon-2-005-cover.jpeg
 ---
 
diff --git a/blog/20251010-postgres-marathon-2-006.md b/blog/20251010-postgres-marathon-2-006.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-006: Mysterious max_locks_per_transaction"
 date: 2025-10-10
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager]
 image: /assets/blog/20251010-postgres-marathon-2-006-cover.png
 ---
 
diff --git a/blog/20251013-postgres-marathon-2-007.md b/blog/20251013-postgres-marathon-2-007.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-007: Should we worry about pg_blocking_pids()'s observer effect?"
 date: 2025-10-13
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks, monitoring]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager, monitoring]
 image: /assets/blog/20251013-postgres-marathon-2-007-cover.jpg
 ---
 
diff --git a/blog/20251014-postgres-marathon-2-008.md b/blog/20251014-postgres-marathon-2-008.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-008: LWLock:LockManager and prepared statements"
 date: 2025-10-14 23:59:59
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks, prepared statements]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager, prepared statements]
 image: /assets/blog/20251014-postgres-marathon-2-008-cover.jpg
 ---
 
diff --git a/blog/20251028-postgres-marathon-2-009.md b/blog/20251028-postgres-marathon-2-009.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-009: Prepared statements and partitioned table lock explosion, part 1"
 date: 2025-10-28 12:00:00
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks, prepared statements, partitioning]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager, prepared statements, partitioning]
 ---
 
 In [#PostgresMarathon 2-008](https://postgres.ai/blog/20251014-postgres-marathon-2-008), we discovered that prepared statements can dramatically reduce `LWLock:LockManager` contention by switching from planner locks (which lock everything) to executor locks (which lock only what's actually used). Starting with execution 7, we saw locks drop from 6 (table + 5 indexes) to just 1 (table only).
diff --git a/blog/20251029-postgres-marathon-2-010.md b/blog/20251029-postgres-marathon-2-010.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-010: Prepared statements and partitioned table lock explosion, part 2"
 date: 2025-10-29 23:59:59
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks, prepared statements, partitioning]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager, prepared statements, partitioning]
 ---
 
 In [#PostgresMarathon 2-009](https://postgres.ai/blog/20251028-postgres-marathon-2-009), we focused on Lock Manager's behavior when dealing with prepared statements and partitioned tables. 
diff --git a/blog/20251030-postgres-marathon-2-011.md b/blog/20251030-postgres-marathon-2-011.md
@@ -2,7 +2,7 @@
 title: "#PostgresMarathon 2-011: Prepared statements and partitioned tables — the paradox, part 3"
 date: 2025-10-30 23:59:59
 authors: nik
-tags: [Postgres insights, PostgresMarathon, internals, locks, prepared statements, partitioning]
+tags: [Postgres insights, PostgresMarathon, internals, locks, lockmanager, prepared statements, partitioning]
 ---
 
 In [#PostgresMarathon 2-009](https://postgres.ai/blog/20251028-postgres-marathon-2-009) and [#PostgresMarathon 2-010](https://postgres.ai/blog/20251029-postgres-marathon-2-010), we explored why execution 6 causes a lock explosion when building a generic plan for partitioned tables — the planner must lock all 52 relations because it can't prune without parameter values.
