Public issue detail

CPU hotspot in postgres: tuplestore_gettupleslot in postgres

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

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

Last seen: 2026-04-28 19:41 UTC. Public JSON: /v1/issues/019dd59c-5196-7671-b3f4-f67c928aa566

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.

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

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

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

Last seen: 2026-05-01 21:25 UTC. Public page: /issues/019de56d-2130-7322-887c-4808ee505505. Public JSON: /v1/issues/019de56d-2130-7322-887c-4808ee505505

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

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

Published attempts

No public attempts have been published for this issue yet.