i should do to avoid this issue in the future ?
On Mon, 9 Dec 2019, 20:05 Robert Haas, wrote:
> On Mon, Dec 9, 2019 at 4:52 AM rajesh kumar
> wrote:
> > We recently started seeing an error “ERROR: uncommitted xmin 347341220
> from before xid cutoff 967029200 needs to be froz
On Mon, Dec 9, 2019 at 11:21 AM rajesh kumar wrote:
> 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 o
On Mon, Dec 9, 2019 at 4:52 AM rajesh kumar 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
Hi All,
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
