Re: Avoiding Refreezing XIDs Repeatedly - Mailing list pgsql-performance

From Alvaro Herrera
Subject Re: Avoiding Refreezing XIDs Repeatedly
Date
Msg-id 20150209185305.GF3391@alvh.no-ip.org
Whole thread Raw
In response to Re: Avoiding Refreezing XIDs Repeatedly  (bkrug <bkrug@usatech.com>)
List pgsql-performance
bkrug wrote:
> Matheus de Oliveira wrote
> > It changed in recent versions (9.3 or 9.4, I don't recall exactly which)
> > and moved to tuple header, but what you described is exactly what was
> > done,
> > the xid was 2.
>
> Should the relfrozenxid of pg_class then equal 2 for very old and already
> vacuumed tables? Because that is not what I am seeing.

No.  The problem is that it's not easy to change the relfrozenxid when
an INSERT/UPDATE command creates a tuple with a non-frozen XID.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-performance by date:

Previous
From: bkrug
Date:
Subject: Re: Avoiding Refreezing XIDs Repeatedly
Next
From: Matheus de Oliveira
Date:
Subject: Re: Avoiding Refreezing XIDs Repeatedly