Hi, On Mon, Jun 22, 2026 at 4:09 AM Jeyaprakash Rajamani <[email protected]> wrote: > > Hi, > > > INFO: analyzing "q_cps_mdm_dm.stg_loader_analze5" > > INFO: "stg_loader_analze5": scanned 30000 of 2563909 pages, containing > > 40373 live rows and 39122 dead rows; 30000 rows in sample, 3450423 > > estimated total rows > > In the sample that ANALYZE saw, about half the rows are dead and > the other half are live. > > That's a lot of bloat. You may want to wait a little bit more for older > transactions to go away (or slots to move forward, if you have any) > before running this vacuum. > > Are there any other solutions to resolve this?
It's hard to make specific suggestions without understanding the actual root cause - what those older transactions are doing and when they started. I would recommend checking pg_stat_activity and reading through the vacuum documentation: https://www.postgresql.org/docs/current/routine-vacuuming.html. -- Bharath Rupireddy Amazon Web Services: https://aws.amazon.com
