What does "modified frequently" actually mean?

[lucasmarcelli]

IVM is effective when we want to keep an IMMV up-to-date and small fraction of a base table is modified infrequently. Due to the overhead of immediate maintenance, IVM is not effective when a base table is modified frequently.

What does frequently mean in this context? Specifically for IVM is not effective when a base table is modified frequently. If I'm inserting/updating thousands of rows per hour on one or more base table, is this too frequent? The size of the base tables are in the 100-1000k rows range, so the proportion of updates is relatively low compared to the totals.

[yugo-n]

What does frequently mean in this context? Specifically for IVM is not effective when a base table is modified frequently.

This mean that pg_ivm causes low performance of base table modification due to the overhead, so pg_ivm is not suitable for use cases where the response time of table modification is crucial. If the table is modified frequently with the interval shorter than the response time, the impact on performance would be larger.

If I'm inserting/updating thousands of rows per hour on one or more base table, is this too frequent? The size of the base tables are in the 100-1000k rows range, so the proportion of updates is relatively low compared to the totals.

What frequency is acceptable would depend on the actual response time of table modification. You will need to make a performance measurement to know it.