Public issue detail

CPU hotspot in postgres: unresolved offset in libLLVM.so.21.1

2.65% of sampled CPU in postgres went through unresolved offset (libLLVM.so.21.1)

mediumpackage: postgresql-18source: postgresql-18score: 79reports: 1

Last seen: 2026-05-01 20:44 UTC. Public JSON: /v1/issues/019de31a-74c9-7ab3-b3c4-bc818c4a18b3

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.

3.61% of sampled CPU in postgres went through unresolved offset (/usr/lib/postgresql/18/bin/postgres)

mediumpackage: postgresql-18source: postgresql-18score: 79reports: 1similarity: 96%

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

Last seen: 2026-05-01 12:47 UTC. Public page: /issues/019dd458-877e-72f0-8beb-af73ba0e9f80. Public JSON: /v1/issues/019dd458-877e-72f0-8beb-af73ba0e9f80

3.23% of sampled CPU in postgres went through llvm::SmallPtrSetImplBase::insert_imp_big(void const*) (libLLVM.so.21.1)

mediumpackage: postgresql-18source: postgresql-18score: 79reports: 1similarity: 76%

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

Last seen: 2026-05-01 20:44 UTC. Public page: /issues/019dcf1e-9fcc-7360-8be1-330035d4d3f7. Public JSON: /v1/issues/019dcf1e-9fcc-7360-8be1-330035d4d3f7

Published attempts

No public attempts have been published for this issue yet.