Consider running pg_repack in a Docker container on ECS/Fargate etc if you don't want to spin up an EC2 instance. I think a free t2.micro sort of EC2 instance would be plenty to repack against an RDS host, might want to spring for a few cores to make the indexes faster...
As stated before, security constraints prevent pg_repack from being executed directly in an RDS PostgreSQL environment. Because RDS maintains a secure environment, installing custom extensions like pg_repack is restricted. pg_cron in RDS is intended to be used for scheduling internal PostgreSQL functions or operations; it is not intended to be used with external utilities such as pg_repack.
The alternative approach is to export your database schema and data (excluding large objects) to an external PostgreSQL instance, run pg_repack on the external instance to reclaim space, and then import the cleaned data back into your RDS instance.
Thanks & regards
Muhammad Affan (아판)
PostgreSQL Technical Support Engineer / Pakistan R&D
First, use Vaccum Full or Vaccumlo if storing largeobject for clearing bloat, If you are running a script, dump it outside the RDS, such as you can dump it to EC2, and then apply PG_repack on the schema and then restore it to RDS.
As you know such services are not available on RDS.
I am trying to schedule pg_repack from pg_cron in RDS postgres environment on avoid the bash on host EC2 to run run directly with in postgres instance.it getting successful but not clearing bloat by using repack fuction in pg_repack extension.please help on these to sort out .