Public issue detail

Runaway CPU investigation for postgres: busy poll at sqlite3VdbeExec

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

highscore: 106reports: 1

Last seen: 2026-10-02 18:03 UTC. Public JSON: /v1/issues/019f9de5-ae93-70a0-b43c-cc5fcfe33721

Technical snapshot

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

Representative thread backtrace

  • Command: /usr/lib/postgresql/12/bin/postgres -D /var/lib/postgresql/12/main -c config_file=/etc/postgresql/12/main/postgresql.conf
  • 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 0x00007f3dd70ac60d in select () 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
0x00007f3dd70ac60d in select () from target:<path>
0x000055b08d00a416 in ?? ()
0x000055b08d00c0c4 in PostmasterMain ()
0x000055b08cd2a375 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.

Runaway CPU investigation for postgres: busy poll at __pte_offset_map_lock

possible duplicate

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: 83%

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

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

Runaway CPU investigation for postgres: busy poll at psi_task_switch

possible duplicate

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

highsource: linuxscore: 106reports: 1similarity: 83%

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

Last seen: 2026-10-16 06:35 UTC. Public page: /issues/01a1383d-aefb-7940-ab82-04e5a3259603. Public JSON: /v1/issues/01a1383d-aefb-7940-ab82-04e5a3259603

Runaway CPU investigation for postgres: busy poll at PreCommit_on_commit_actions

possible duplicate

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: 82%

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

Last seen: 2026-10-22 19:28 UTC. Public page: /issues/019e5105-5337-7b80-ade1-c7185ee1c6f2. Public JSON: /v1/issues/019e5105-5337-7b80-ade1-c7185ee1c6f2

Runaway CPU investigation for perl: busy poll at perf_ctx_enable

possible duplicate

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

highpackage: perl-basesource: perlscore: 106reports: 2successful triagesimilarity: 78%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-10-22 19:28 UTC. Public page: /issues/019e4743-6f51-7fc1-b372-9900d37706a1. Public JSON: /v1/issues/019e4743-6f51-7fc1-b372-9900d37706a1

Runaway CPU investigation for python3.13: busy poll at read_tsc

possible duplicate

python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through read_tsc, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () from target:<path>.

highpackage: python3.13-minimalsource: python3.13score: 106reports: 2successful triagesimilarity: 78%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-10-10 01:56 UTC. Public page: /issues/019da8df-cd0c-7880-ab1e-6dd908d64437. Public JSON: /v1/issues/019da8df-cd0c-7880-ab1e-6dd908d64437

Runaway CPU investigation for python3.13: busy poll at idle_cpu

possible duplicate

python3.13 is stuck in a likely busy poll loop: 40.65% of sampled CPU passed through idle_cpu, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () from target:<path>.

highpackage: python3.13-minimalsource: python3.13score: 106reports: 2successful triagesimilarity: 77%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-10-04 02:36 UTC. Public page: /issues/019dfead-0293-7062-b24e-c9b04c2f1edb. Public JSON: /v1/issues/019dfead-0293-7062-b24e-c9b04c2f1edb

Published attempts

No public attempts have been published for this issue yet.

Quarantine stays on by default so the public queue is harder to spam.