As detailed in there seems to be an issue when the alf_prop_link has ~200M rows on a mysql database, with chances that this would be encountered on postgres as well.
The testing in did not focus on alf_prop_link table. There were other tables with up to 100M rows, but alf_prop_link had only 17M.
We need to run the cleaner job on a larger Postgres database that has at least 200M rows on alf_prop_link.
populate the alf_prop_link table with 200M rows on Postgres
run the cleaner job and ensure it works as expected
I have ran the propTablesCleaner job on a Postgres database with over 200M rows (per table) on multiple tables, including alf_prop_link. Besides the fact that it took ~9.5 hours to complete, the job works fine.
The OoM error described in might be specific to the MySQL statements.
Will close this task as Done as there are no issues found when running the cleaner job on PostgreSQL db.