From: | Daulat <daulat(dot)dba(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | 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 08:11:31 |
Message-ID: | CALfOM6KRUw-6Qo-mSBvyBBtACZPPcQtUsPYjbANiZ_Rv-CR+Hw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
We are unable to take the backup of our database. While taking backup we
are getting the same error.
psql: error: connection to server at "localhost" (::1), port 5014 failed:
FATAL: pg_attribute catalog is missing 1 attribute(s) for relation OID 2662
Thanks.
On Fri, Mar 22, 2024 at 12:35 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-03-22 10:09:29 | Re: uncommitted xmin 3100586 from before xid cutoff 10339367 needs to be frozen |
Previous Message | arun chirappurath | 2024-03-22 07:13:40 | pg_locks-exclusivelock for select queries |