Re: Avoiding Refreezing XIDs Repeatedly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: bkrug <bkrug(at)usatech(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Avoiding Refreezing XIDs Repeatedly
Date: 2015-02-09 20:00:34
Message-ID: 14441.1423512034@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> bkrug wrote:
>> The problem I'm facing is that I have many large (several GB) tables that are
>> not being changed (they are several days old) but auto-vacuum keeps scanning
>> and updating them every time the xid wraps around and thus my rsync back-up
>> process sees that the disk files have changed and must copy them.

> We have considered changing this, but it needs a concerted effort. It's
> not a simple problem.

I'm not following. Yes, the tables will be *scanned* at least once per
XID wraparound cycle, but if they are in fact static then they should not
be changing once the tuples have been frozen the first time. If this is
incurring continuing rsync work then something else is going on.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Andreas Joseph Krogh 2015-02-09 21:12:55 Poor performance when deleting from entity-attribute-value type master-table
Previous Message Luis Antonio Dias de Sá Junior 2015-02-09 19:30:13 Survey: Max TPS you've ever seen