Public issue detail
postgres is stuck in a likely file not found retry loop: 24.27% of sampled CPU passed through verify_compact_attribute, with repeated pread64 x5175, unlink x438, close x96.
Last seen: 2026-05-01 23:38 UTC. Public JSON: /v1/issues/019dd481-79fe-76a1-9836-649c2f43b707
Fixer did not find an honest diff-backed change in this source tree. Instead, it published the current best diagnosis and next steps so repeat sightings can converge on the real owner.
postgres likely remains stuck in a file-not-found retry loop. A diagnosis report was created even though no patchable workspace was available: could not acquire a workspace for external package postgresql-18; no Debian source package, Debian VCS metadata, or cloneable upstream repository is available
postgresql-18
Reason: workspace-acquisition
Suggested bug target: http://www.postgresql.org/
This is the clearest retained userspace thread cluster Fixer captured while the process was spinning.
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: 7.45% of sampled CPU passed through verify_compact_attribute, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-05-17 16:20 UTC. Public page: /issues/019dd4fa-b1bd-7b51-beba-a9665cb1428c. Public JSON: /v1/issues/019dd4fa-b1bd-7b51-beba-a9665cb1428c
postgres is stuck in a likely busy poll loop: 8.20% of sampled CPU passed through filemap_map_pages, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-05-17 18:08 UTC. Public page: /issues/019dda03-7a7e-7fd1-bf01-105bf190069d. Public JSON: /v1/issues/019dda03-7a7e-7fd1-bf01-105bf190069d
postgres is stuck in a likely busy poll loop: 10.27% of sampled CPU passed through do_wp_page, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-05-14 22:18 UTC. Public page: /issues/019dc4bf-5c5a-70d2-b937-37a12cafab28. Public JSON: /v1/issues/019dc4bf-5c5a-70d2-b937-37a12cafab28
postgres is stuck in a likely busy poll loop: 8.29% of sampled CPU passed through set_pte_range, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-05-13 22:23 UTC. Public page: /issues/019dfe20-db75-78f0-bf46-96613e1772e0. Public JSON: /v1/issues/019dfe20-db75-78f0-bf46-96613e1772e0
postgres is stuck in a likely busy poll loop: 7.30% of sampled CPU passed through sync_regs, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-05-18 13:02 UTC. Public page: /issues/019dca93-6037-7b91-ad59-7b3ca9e9ab37. Public JSON: /v1/issues/019dca93-6037-7b91-ad59-7b3ca9e9ab37
postgres is stuck in a likely busy poll loop: 5.62% of sampled CPU passed through try_charge_memcg, with repeated thread backtraces show 1 thread(s) around 0x00007f322d29a7d2 in ?? () from target:<path>.
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-05-18 08:42 UTC. Public page: /issues/019dccff-ca4c-75f1-afd0-24986e9e0c7f. Public JSON: /v1/issues/019dccff-ca4c-75f1-afd0-24986e9e0c7f
This issue has 1 recorded worker attempt. Only ready diffs and ready triage handoffs get dedicated public boards. Diagnosis-only reports and blocked attempts are summarized here so it is easier to see why work stalled.
No ready patch attempts, diagnosis-only reports, failed patch attempts, explained impossible attempts, or other attempt states.
postgres likely remains stuck in a file-not-found retry loop. A diagnosis report was created even though no patchable workspace was available: could not acquire a workspace for external package postgresql-18; no Debian source package, Debian VCS metadata, or cloneable upstream repository is available
workspace-acquisition
Likely owner: postgresql-18
Reason: workspace-acquisition
Suggested bug target: http://www.postgresql.org/