On Tue, Apr 23, 2024 at 06:33:48PM +0200, Matthias van de Meent wrote: > I've heard of use cases where dumping stats without data would help > with production database planner debugging on a non-prod system. > > Sure, some planner inputs would have to be taken into account too, but > having an exact copy of production stats is at least a start and can > help build models and alerts for what'll happen when the tables grow > larger with the current stats. > > As for other planner inputs: table size is relatively easy to shim > with sparse files; cumulative statistics can be copied from a donor > replica if needed, and btree indexes only really really need to > contain their highest and lowest values (and need their height set > correctly).
Is it possible to prevent stats from being updated by autovacuum and other methods? -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.
