Sam Hames

Currently: “Content.”

A Hairy PostgreSQL Incident | Ardent Performance Computing

https://ardentperf.com/2022/02/10/a-hairy-postgresql-incident/

It was a bad query plan, causing PostgreSQL to build a bitmap over an entire index to use only part of the results - and temporarily solved by using a CTE as an optimisation fence (but note that that behaviour changed as of version 12).

Tags

Related By Tags

Details

Revised
Created
Edited