Public issue detail

CPU hotspot in postgres: AllocSetCheck in postgres

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

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

Last seen: 2026-05-01 12:09 UTC. Public JSON: /v1/issues/019d4b44-edab-7c50-91f6-eee464318283

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.95% of sampled CPU in postgres went through AllocSetAlloc (/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, very similar public summary

Last seen: 2026-04-30 21:08 UTC. Public page: /issues/019dd9b3-4e9f-78c0-a119-eff668a597c6. Public JSON: /v1/issues/019dd9b3-4e9f-78c0-a119-eff668a597c6

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

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

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

Last seen: 2026-04-29 07:24 UTC. Public page: /issues/019dd820-5443-7340-bf54-2e209d97f24a. Public JSON: /v1/issues/019dd820-5443-7340-bf54-2e209d97f24a

Published attempts

No public attempts have been published for this issue yet.