2 ms·
Puzzling Postgres: a story of solving an unreproducible performance issue
- rekahrv 4y agoAn awesome article. 3 surprises around Postgres and a detailed description of the investigation leading to them. "we had a query that was particularly slow in production, but it was very hard to reproduce as we didn’t know our ORM was using prepared statements under the hood and nothing was looking problematic with a simple EXPLAIN ANALYZE."
- egamirorrim 4y agoThis is indeed a fascinating read. What I'd love to have is a "how can I spot this happening with my queries in production"? Most libraries I've used as an API developer prepare queries, it's a great peace of mind for SQL injection attacks where you're dealing with user input - so this could be happening in my app and I wouldn't even know about it! What do you think the downside of just defensively enabling force_custom_plan is, if any?