I meant the anaylze, if anaylze will run very often on the original table, arent there disadvantages for it ?
בתאריך יום ד׳, 13 בפבר׳ 2019 ב-18:54 מאת Alvaro Herrera <alvherre@xxxxxxxxxxxxxxx>:
On 2019-Feb-13, Mariel Cherkassky wrote:
> To be honest, it isnt my db, but I just have access to it ...
Well, I suggest you forget the password then :-)
> Either way, so I need to change the vacuum_Analyze_scale/threshold for the
> original table ? But the value will be too high/low for the original table.
> For example if my original table has 30,000 rows and my toasted has
> 100,000,000 rows. I want to analyze every 50K records in the toasted (by
> the way, sounds legit ?) which is 0.05% of 100m. With this value it means
> that every 0.05*30,000=1500 updated/deletes on the original table it will
> run analyze on the original table which is very often...
> Doesn't it seems a little bit problematic ?
Autovacuum considers main table and toast table separately for
vacuuming, so nothing you do to the parameters for the main table will
affect the vacuuming schedule of the toast table.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
