Re: ERROR: uncommitted xmin 347341220 from before xid cutoff 967029200 needs to be frozen

Hi Robert,

Thanks for your reply.
So, i have this question. I have seen a patch on similar issue with shared
catalog tables and it is fixed in PostgreSQL 9.6.10.
We are currently using 9.6.10.
Do you think we hit another bug ?
Is this because of some synchronization issue ?

Or is there something i should do to avoid this issue in the future ?

On Mon, 9 Dec 2019, 20:05 Robert Haas, <robertmhaas(at)gmail(dot)com> wrote:

> On Mon, Dec 9, 2019 at 4:52 AM rajesh kumar <vallarapurajesh(at)gmail(dot)com>
> wrote:
> > We recently started seeing an error “ERROR: uncommitted xmin 347341220
> from before xid cutoff 967029200 needs to be frozen” on our user tables.
> > I’m unable to do ‘vacuum’, ‘vacuum freeze’ or ‘vacuum full’ on the
> affected tables.
> >
> > From what I read, this was a bug couple of years ago on System tables
> and it was fixed long back.
> > However, we are seeing these errors on two of our User tables now.
> >
> > After some Google search, I found the fix but, they seem to be temporary.
> >
> > These are the solutions I found :
> > 1. Truncate the table and restore the dump
> >
> > 2. remove ‘pg_internal.init’ from global directory
> >
> >
> > I’m not yet sure about removing the file ‘pg_internal.init’. So, I
> would go ahead with table rebuilt for now.
> >
> > Anyways, I would like to know if there is any permanent solution for
> this issue as I did not find a proper solution.
>
> I think that the best thing to do would be to dump all of your data
> using pg_dump, create a whole new cluster using initdb, restore the
> data into the new cluster, and delete the old one.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>