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
- ๐ Some SQL Tricks of an Application DBA | Haki Benita
- ๐ The Vietnam of Computer Science ยท Ted Neward's Blog
- ๐ Game UI Database | Welcome
- ๐ Citus 10: Columnar for Postgres, rebalancer, single-node, & more
- ๐ ORM Annoyances
- ๐ (A few) Ops Lessons We All Learn The Hard Way
- ๐ Wesley Aptekar-Cassels | Things I Believe About Software Engineering
- ๐ Engineering | BestPracticer
- ๐ Sorry for all the Drupal: Reflections on the 3rd anniversary of "Drupal for Humanists" | Quinn Dombrowski
- ๐ Computer Files Are Going Extinct - OneZero
Details
- Revised
- Created
- Edited