Sam Hames

A Hairy PostgreSQL Incident | Ardent Performance Computing

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).