Public issue detail

Runaway CPU investigation for postgres: file not found retry at pglz_decompress

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

highscore: 106reports: 1

Last seen: 2026-10-13 05:43 UTC. Public JSON: /v1/issues/019fa653-58fc-7d62-b84f-1f51afcbf926

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.nxadCO/data -F -h -p 23014 -k /tmp/postgis-pg14.nxadCO/socket -c fsync=off -c full_page_writes=off -c synchronous_commit=off
  • Why Fixer classified it this way: The trace keeps retrying file lookups that fail with ENOENT, which suggests a missing-file retry loop.
  • Thread summary: thread backtraces show 1 thread(s) around 0x00007f92e0a4e687 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: mmap -> mmap -> mmap
  • Top syscalls: mmap x9785, read x7490, openat x4511, close x3432
  • Kernel: 7.1.8+deb14.1-amd64
  • Distribution: debian
0x00007f92e0a4e687 in __GI__IO_flush_all () from target:<path>
0x00007f92e0a4e6ad in __GI__IO_flush_all () from target:<path>
0x00007f92e0acd1d9 in select () from target:<path>
0x000055df43efce5f in ?? ()
0x000055df43efe77f in PostmasterMain ()
0x000055df43c6044c 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: file not found retry at unresolved offset in postgres

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-10-13 06:22 UTC. Public page: /issues/019f77a0-05cc-7ca2-84d1-d756b2e2db54. Public JSON: /v1/issues/019f77a0-05cc-7ca2-84d1-d756b2e2db54

Runaway CPU investigation for postgres: file not found retry at malloc

possible duplicate

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

highscore: 106reports: 1similarity: 99%

Why this looks related: same classification, same subsystem, same target, very similar public summary

Last seen: 2026-10-13 06:02 UTC. Public page: /issues/01a133a7-70dc-73b3-b590-4cd62ec20ac9. Public JSON: /v1/issues/01a133a7-70dc-73b3-b590-4cd62ec20ac9

Runaway CPU investigation for postgres: file not found retry at __strncat_avx2_rtm

possible duplicate

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

highscore: 106reports: 1similarity: 99%

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

Last seen: 2026-10-02 08:38 UTC. Public page: /issues/01a0f645-98ad-79e2-91aa-24280b548c45. Public JSON: /v1/issues/01a0f645-98ad-79e2-91aa-24280b548c45

Runaway CPU investigation for postgres: file not found retry at hash_search_with_hash_value

possible duplicate

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

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

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

Last seen: 2026-10-02 10:33 UTC. Public page: /issues/019f78b9-d301-7792-a0ea-d9bb6a05f05c. Public JSON: /v1/issues/019f78b9-d301-7792-a0ea-d9bb6a05f05c

Runaway CPU investigation for postgres: file not found retry at XLogNeedsFlush

possible duplicate

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

highscore: 106reports: 1similarity: 93%

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

Last seen: 2026-09-30 03:07 UTC. Public page: /issues/01a0ee1d-0385-77b3-8bf7-d516edc62f39. Public JSON: /v1/issues/01a0ee1d-0385-77b3-8bf7-d516edc62f39

Runaway CPU investigation for postgres: file not found retry at WaitEventSetWait

possible duplicate

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

highscore: 106reports: 1similarity: 92%

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

Last seen: 2026-09-28 15:51 UTC. Public page: /issues/01a0e840-352c-74f0-a516-88ac9cf0a1d0. Public JSON: /v1/issues/01a0e840-352c-74f0-a516-88ac9cf0a1d0

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.