On Monday, April 18, 2022, bhargav kamineni <kbn98...@gmail.com> wrote:
> Hi Team, > > It seems vacuum is behaving somewhat weird on postgres database , > observing below HINTS on the vacuum logs > > WARNING: oldest xmin is far in the past > > HINT: Close open transactions soon to avoid wraparound problems. > > You might also need to commit or roll back old prepared transactions, or > drop stale replication slots. > > > What version? What other databases are present? Others can give better (more detailed/nuanced) guidance but if you can just start vacuuming every table in every database manually, you probably should just do that. Vacuum freeze specifically. David J.
