Public issue detail

Runaway CPU investigation for postgres: busy poll at LockBufHdr

postgres is stuck in a likely busy poll loop: 25.00% of sampled CPU passed through LockBufHdr, with repeated thread backtraces show 1 thread(s) around 0x00007f35853ee687 in __GI__IO_flush_all () from target:<path>.

highpackage: postgresql-18source: postgresql-18score: 106reports: 1

Last seen: 2026-11-05 14:14 UTC. Public JSON: /v1/issues/019dc250-4c8b-7812-88a9-0d10a9b035ea

Technical snapshot

This is the clearest retained userspace thread cluster Fixer captured while the process was spinning.

Representative thread backtrace

  • Command: /usr/lib/postgresql/14/bin/postgres -D /tmp/postgis-pg14.Zqc2Fq/data -F -h -p 33607 -k /tmp/postgis-pg14.Zqc2Fq/socket -c fsync=off -c full_page_writes=off -c synchronous_commit=off
  • Why Fixer classified it this way: The trace repeatedly returns to a poll-family syscall without meaningful blocking, which suggests a busy event-loop wakeup.
  • Thread summary: thread backtraces show 1 thread(s) around 0x00007f35853ee687 in __GI__IO_flush_all () from target:<path>
  • Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory. warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable. Connect to gdbserver inside the container. warning: Expected absolute pathname for libpthread in the inferior, but got target:<path> warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
  • Repeated loop: pselect6
  • Top syscalls: pselect6 x1
  • Kernel: 7.1.8+deb14.1-amd64
  • Distribution: debian
0x00007f35853ee687 in __GI__IO_flush_all () from target:<path>
0x00007f35853ee6ad in __GI__IO_flush_all () from target:<path>
0x00007f358546d1d9 in select () from target:<path>
0x000055603594be5f in ?? ()
0x000055603594d77f in PostmasterMain ()
0x00005560356af44c in main ()

Possible duplicates

These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.

postgres is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through PreCommit_on_commit_actions, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

highpackage: postgresql-18source: postgresql-18score: 106reports: 2similarity: 99%

Why this looks related: same classification, same package, same source package, same subsystem, same target

Last seen: 2026-11-22 12:52 UTC. Public page: /issues/019e5105-5337-7b80-ade1-c7185ee1c6f2. Public JSON: /v1/issues/019e5105-5337-7b80-ade1-c7185ee1c6f2

postgres is stuck in a likely busy poll loop: 7.33% of sampled CPU passed through __pte_offset_map_lock, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

highpackage: postgresql-18source: postgresql-18score: 106reports: 2successful triagesimilarity: 99%

Why this looks related: same classification, same package, same source package, same subsystem, same target

Last seen: 2026-10-31 10:54 UTC. Public page: /issues/019e50c1-4b02-72f3-8479-d67944473579. Public JSON: /v1/issues/019e50c1-4b02-72f3-8479-d67944473579

postgres is stuck in a likely file not found retry loop: 3.27% of sampled CPU passed through hash_search_with_hash_value, with repeated thread backtraces show 1 thread(s) around 0x00007f5bf1686687 in __GI__IO_flush_all () from target:<path>.

highpackage: postgresql-18source: postgresql-18score: 106reports: 1similarity: 88%

Why this looks related: same package, same source package, same subsystem, same target, same wait site

Last seen: 2026-11-07 03:43 UTC. Public page: /issues/019f78b9-d301-7792-a0ea-d9bb6a05f05c. Public JSON: /v1/issues/019f78b9-d301-7792-a0ea-d9bb6a05f05c

postgres is stuck in a likely file not found retry loop: 2.86% of sampled CPU passed through cfree, with repeated thread backtraces show 1 thread(s) around 0x00007f0fa9a89687 in __GI__IO_flush_all () from target:<path>.

highpackage: postgresql-18source: postgresql-18score: 106reports: 1similarity: 85%

Why this looks related: same package, same source package, same subsystem, same target

Last seen: 2026-11-06 22:28 UTC. Public page: /issues/019f9a81-885e-7ec2-b01c-c77080774c0a. Public JSON: /v1/issues/019f9a81-885e-7ec2-b01c-c77080774c0a

postgres is stuck in a likely socket churn loop: 2.04% of sampled CPU passed through next_uptodate_folio, with repeated thread backtraces show 1 thread(s) around 0x00007f520c1d6687 in __GI__IO_flush_all () from target:<path>.

highpackage: postgresql-18source: linuxscore: 106reports: 1similarity: 84%

Why this looks related: same package, same subsystem, same target, same wait site

Last seen: 2026-10-29 11:21 UTC. Public page: /issues/019f777c-b6c6-73c1-9b2a-9e06e91c6ca9. Public JSON: /v1/issues/019f777c-b6c6-73c1-9b2a-9e06e91c6ca9

postgres is stuck in a likely timer churn loop: 100.00% of sampled CPU passed through start_dl_timer, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.

highpackage: postgresql-18source: postgresql-18score: 106reports: 2successful triagesimilarity: 84%

Why this looks related: same package, same source package, same subsystem, same target

Last seen: 2026-11-08 17:37 UTC. Public page: /issues/019e5d7e-79c8-70a3-bcbd-6d4643b9285a. Public JSON: /v1/issues/019e5d7e-79c8-70a3-bcbd-6d4643b9285a

Published attempts

No public attempts have been published for this issue yet.