Public issue detail

CPU hotspot in postgres: MemoryContextReset in postgres

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

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

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

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.77% of sampled CPU in postgres went through index_form_tuple_context (/usr/lib/postgresql/18/bin/postgres)

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

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

Last seen: 2026-04-30 21:37 UTC. Public page: /issues/019de053-34be-7c50-b88b-4deb733b6f55. Public JSON: /v1/issues/019de053-34be-7c50-b88b-4deb733b6f55

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

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

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.