On Mon, 2025-02-24 at 15:53 -0500, Andres Freund wrote:
> I don't think that's necessarily true, hot pruning might help some,
> as afaict
> the restore happens in multiple transactions.
Yeah, I just dumped and reloaded the regression database with and
without stats, and saw no difference in the resulting size. So it's
probably more correct to say "churn" rather than "bloat".
Even running "psql -1", I see modest bloat substantially less than 2x.
So if we agree that we don't mind a bit of churn and we will never need
this (despite what ANALYZE does), then I'm OK removing it. Which makes
me wonder why ANALYZE does it with inplace updates?
Regards,
Jeff Davis
