Set removal time is creating dead tuples in postgresql database

Camunda 7 Topics Discussion & Questions
1

I’m using camunda 7.18.0 with postgresql database.

After using the API Set Removal Time Async (POST) | docs.camunda.org the database size increases about 2x times. Especially the tables act_hi_detail and act_hi_varinst grow too large after the set-removal-time batch finishes executing the jobs.

SQL to check dead tuples:
select n_live_tup, n_dead_tup from pg_stat_all_tables where relname='act_hi_detail';
returns:

n_live_tup  |  n_dead_tup
18844088    |  3717643

Any idea about how to fix this issue?

2

I had to reindex act_hi_* tables to clean dead tuples