Prabhjot Sheena <prabhjot.sheena@xxxxxxxxxxxxxx> writes: > i will run full vacuum than and see how it goes. I think that is seriously bad advice. It will take longer and not do anything more to resolve your immediate problem --- which, it appears, you don't have a whole lot of time to resolve if you want to avoid a forced shutdown. It would likely be worth your time to figure out which table(s) in which database(s) are actually causing this issue, and vacuum those first, instead of blindly vacuuming everything. This will tell you which database(s) are most problematic: select datname, age(datfrozenxid) from pg_database order by 2 desc; and then within those database(s) you can similarly do select relname, age(relfrozenxid) from pg_class where relkind = 'r' order by 2 desc; to find the most problematic table(s). BTW, did you perhaps turn autovacuum off, or cripple its performance through ill-chosen throttling settings? It really should've kept you out of this problem. regards, tom lane
