Public issue detail

CPU hotspot in postgres: unresolved offset in [JIT]

5.00% of sampled CPU in postgres went through unresolved offset ([JIT])

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

Last seen: 2026-05-01 15:38 UTC. Public JSON: /v1/issues/019dda2b-7c22-7232-8122-f87aaa64c725

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

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

100.00% of sampled CPU in postgres went through MemoryContextReset (/usr/lib/postgresql/18/bin/postgres)

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

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

Last seen: 2026-04-29 15:50 UTC. Public page: /issues/019dd9db-44f0-7f80-a41d-ba4e474e42f0. Public JSON: /v1/issues/019dd9db-44f0-7f80-a41d-ba4e474e42f0

Published attempts

No public attempts have been published for this issue yet.