Post #2847217
2026-05-08 11:49 UTC
@diegor I definitely don't want to use execution time testing. Our tests run in various contexts with wildly varying hardware capabilities, and this would mean a lot of noise - likely much worse for us than keeping up with changes in PostgreSQL.
Replies (1)
-
@cjwatson@mastodon.ie 2026-05-08 11:55
@diegor I agree things like choice of seq scan are situational and data-dependent, of course; none of this is going to be universal, just like many other things one might want to test. Nevertheless, if I've gone through an optimization exercise involving looking at choices of query plans and finding ways to tweak them, that seems like something I want to record somewhere so that it doesn't regress accidentally.