Re: uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Daulat <daulat(dot)dba(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen
Date: 2024-03-22 07:05:53
Message-ID: a332ed10692b4a52efcf9320ad2ea3fe426c448f.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message arun chirappurath 2024-03-22 07:13:40 pg_locks-exclusivelock for select queries
Previous Message Daulat 2024-03-22 05:26:31 uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen