Database size growing unexpectdly after upgrading couchdb to 3.2.2 from 3.1

[NOTE]: # ( ^^ Provide a general summary of the issue in the title above. ^^ )

## Description

[NOTE]: # ( Describe the problem you're encountering. )
[TIP]: # ( Do NOT give us access or passwords to your actual CouchDB! )
Database size growing unexpectdly after upgrading couchdb to 3.2.2 from 3.1
example. we have database called jobs and it went to 256g in 4 days and reduced to 4g after i ran compaction.
## Steps to Reproduce

[NOTE]: # ( Include commands to reproduce, if possible. curl is preferred. )

## Expected Behaviour

[NOTE]: # ( Tell us what you expected to happen. )

## Your Environment

[TIP]: # ( Include as many relevant details about your environment as possible. )
[TIP]: # ( You can paste the output of curl http://YOUR-COUCHDB:5984/ here. )

* CouchDB version used:
* Browser name and version:
* Operating system and version:

## Additional Context

[TIP]: # ( Add any other context about the problem here. )

Start by reviewing the report’s upgrade path from CouchDB 3.1 to 3.2.2 and the example database growth from 4 GB to 256 GB in four days. Reproduce the behavior if possible, then compare database size before and after compaction; the missing reproduction steps and environment details must be established before the issue can be considered resolved.

Written by the indexing model from the issue text.