Re: uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen - Mailing list pgsql-general

From Laurenz Albe
Subject Re: uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen
Date
Msg-id a332ed10692b4a52efcf9320ad2ea3fe426c448f.camel@cybertec.at
Whole thread Raw
In response to uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen  (Daulat <daulat.dba@gmail.com>)
Responses Re: uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen  (Daulat <daulat.dba@gmail.com>)
List pgsql-general
On Fri, 2024-03-22 at 10:56 +0530, Daulat wrote:
> We recently started seeing an error “ERROR:  uncommitted xmin 3100586
> from before xid cutoff 10339367 needs to be frozen” on our user tables.
> I’m unable to do ‘vacuum’, ‘vacuum freeze’ or ‘vacuum full’ on Postgres 14.4 running on a windows environment.
>
> Error:
>
> first come this---- ERROR:  uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen
> CONTEXT:  while scanning block 1403 offset 8 of relation "pg_catalog.pg_attribute"

Update to 14.latest; perhaps that data corruption was caused by a bug that
is already fixed.

Upgrading won't get rid of the error though (I think).
The seasy way is to dump the database and restore it to a new database.

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Daulat
Date:
Subject: uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen
Next
From: arun chirappurath
Date:
Subject: pg_locks-exclusivelock for select queries