Public issue detail

CPU hotspot in postgres: unresolved offset in liblber.so.2.0.200

4.50% of sampled CPU in postgres went through unresolved offset (liblber.so.2.0.200)

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

Last seen: 2026-05-01 07:44 UTC. Public JSON: /v1/issues/019dcb47-39f1-73f2-b7cc-a576beb3670a

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.

CPU hotspot in postgres: unresolved offset in postgres

possible duplicate

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

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

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

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.