Make stats_ext test faster under cache-clobbering test conditions.
Tom Lane <tgl@sss.pgh.pa.us>
Make stats_ext test faster under cache-clobbering test conditions. Commit 1eccb9315 added a test case that will cause a large number of evaluations of a plpgsql function. With -DCLOBBER_CACHE_ALWAYS, that takes an unreasonable amount of time (hours) because the function's cache entries are repeatedly deleted and rebuilt. That doesn't add any useful test coverage --- other test cases already exercise plpgsql well enough --- and it's not part of what this test intended to cover. We can get the same planner coverage, if not more, by making the test directly invoke numeric_lt(). Reported-by: Tomas Vondra <tomas@vondra.me> Author: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/baf1ae02-83bd-4f5d-872a-1d04f11a9073@vondra.me
Files
| Path | Change | +/− |
|---|---|---|
| src/test/regress/expected/stats_ext.out | modified | +3 −7 |
| src/test/regress/sql/stats_ext.sql | modified | +3 −8 |
Discussion
- increased duration of stats_ext tests with -DCLOBBER_CACHE_ALWAYS 10 messages · 2025-12-02 → 2025-12-06