Re: oldest xmin is far in the past :: BUT xmin is not available in system - Mailing list pgsql-general

From Tom Lane
Subject Re: oldest xmin is far in the past :: BUT xmin is not available in system
Date
Msg-id 2555588.1650382729@sss.pgh.pa.us
Whole thread Raw
In response to Re: oldest xmin is far in the past :: BUT xmin is not available in system  (Rob Sargent <robjsargent@gmail.com>)
List pgsql-general
Rob Sargent <robjsargent@gmail.com> writes:
> On 4/19/22 00:06, David G. Johnston wrote:
>> On Monday, April 18, 2022, bhargav kamineni <kbn98406@gmail.com> wrote:
>> 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

> This site has lots of useful queries for this sort of issue:
> https://www.shanelynn.ie/postgresql-find-slow-long-running-and-blocked-queries.
> I think you're looking for a very old transaction that is probably not
> going to finish, must be terminated.

Yeah, that.  Manual vacuuming isn't going to help until you get rid
of the old open transaction.  Look into pg_prepared_xacts and
pg_stat_activity.

            regards, tom lane



pgsql-general by date:

Previous
From: "Thomas, Richard"
Date:
Subject: RE: PostgreSQL 10.20 crashes / Antivirus
Next
From: Peter Geoghegan
Date:
Subject: Re: oldest xmin is far in the past :: BUT xmin is not available in system