A giant table which is never updated (or deleted from) doesn't need to be vacuumed.
That same giant table which isn't added to anymore doesn't need to be analyzed, either.
On 3/12/23 15:34, Joseph Hammerman wrote:
Hi all,
Apologies for any confusion I may have caused. What I am imagining is per table tuning that buckets the tables based on their relative sizes.
Something like:
Up to 1Gb - Small
Up to 4Gb - Medium
Up to 8Gb - L
Bigger - XL
And an accordant autovacuum_scale_factor associated with each size.
The motivation for this is to make sure large tables get regularly vacuumed.
I hope that clears thing up!
Joe
I think Mr Hammerman is referring to T-shirts for user stories.
But even when I'm right I don't get what is meant with that. I don't get what Joe means with "autovacuuming profiles per table". Joe, can you elaborate on that?
Yours
Wolfgang
On Sat, 2023-03-11 at 10:49 -0800, Joseph Hammerman wrote:
> I would like to define t-shirt sizes and have an autovacuuming profile associated with each t-shirt size.
>
> Is there any tooling out there that assists in the execution side of this? Or are all of you rolling your own?
Isn't that question 21 days early?
Yours,
Laurenz Albe
--
Born in Arizona, moved to Babylonia.
