Skip to content

Add lockmanager tag to PostgresMarathon LWLock:LockManager posts#32

Draft
NikolayS wants to merge 2 commits into
masterfrom
claude/add-lockmanager-tag-rp9Dy
Draft

Add lockmanager tag to PostgresMarathon LWLock:LockManager posts#32
NikolayS wants to merge 2 commits into
masterfrom
claude/add-lockmanager-tag-rp9Dy

Conversation

@NikolayS
Copy link
Copy Markdown
Contributor

Summary

Adds a unified lockmanager tag to the PostgresMarathon 2 blog posts that explore LWLock:LockManager, so they can be grouped together via a single tag.

Tagged posts:

  • 2-001: Lightweight and heavyweight locks
  • 2-002: Relation-level locks
  • 2-003: The roots of LWLock:LockManager
  • 2-004: Fast-path locking explained
  • 2-005: More LWLock:LockManager benchmarks for Postgres 18
  • 2-006: Mysterious max_locks_per_transaction (the example from the request)
  • 2-007: Should we worry about pg_blocking_pids()'s observer effect?
  • 2-008: LWLock:LockManager and prepared statements
  • 2-009: Prepared statements and partitioned table lock explosion, part 1
  • 2-010: Prepared statements and partitioned table lock explosion, part 2
  • 2-011: Prepared statements and partitioned tables — the paradox, part 3

Skipped 2-012 (pgBackRest replica creation) and 2-013 (indexes), which are not about LockManager.

Test plan

  • Verify the lockmanager tag page lists all 11 posts after build
  • Confirm no other frontmatter or rendering regressed

Generated by Claude Code

@NikolayS NikolayS closed this May 11, 2026
@NikolayS NikolayS reopened this May 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants