| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | bhargav kamineni <kbn98406(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: oldest xmin is far in the past :: BUT xmin is not available in system |
| Date: | 2022-04-19 06:06:11 |
| Message-ID: | CAKFQuwaQsMFvvuK=1GZfaA2Mw1oOcd7tMpyzCCKkD986fVCTGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday, April 18, 2022, bhargav kamineni <kbn98406(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bhargav kamineni | 2022-04-19 06:37:09 | Re: oldest xmin is far in the past :: BUT xmin is not available in system |
| Previous Message | bhargav kamineni | 2022-04-19 05:44:40 | oldest xmin is far in the past :: BUT xmin is not available in system |