![]() This will show cumulative counts since the last time you called the function pg_stat_reset().Ĭheck if n_tup_hot_upd (the HOT update count) grows about as fast as n_tup_upd (the update count) to see if you get the HOT updates you want. There is a simple way to see if your setting is effective and if you get HOT updates: ![]() But you can use VACUUM (FULL) or CLUSTER to rewrite the table, which will respect the new fillfactor setting. Note that setting fillfactor on an existing table will not rearrange the data, it will only apply to future INSERTs. The best value for fillfactor will depend on the size of the average row (larger rows need lower values) and the workload. If you choose a value less than the default 100, you can make sure that there is enough room for HOT updates in each table block. It is a value between 10 and 100 and determines to which percentage INSERTs will fill a table block. You can make sure that the second condition from above is satisfied, but how can you make sure that there is enough free space in table blocks? For that, we have the storage parameter fillfactor. Using fillfactor on tables to get HOT updates The second condition is not obvious and is required by the current implementation of the feature.
0 Comments
Leave a Reply. |