Re: Recalculating OldestXmin in a long-running vacuum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Recalculating OldestXmin in a long-running vacuum
Date: 2007-01-16 16:31:26
Message-ID: 21171.1168965086@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> It seems to me that we could easily reclaim a bit more dead tuples in a
> vacuum by recalculating the OldestXmin every now and then.

Doesn't this break relfrozenxid maintenance? In any case I'd like to
see some evidence of significant real-world benefit before adding such
a conceptual wart ...

The procarray.c change scares me as well; I'm pretty sure the original
coding was intentional.

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Heikki Linnakangas 2007-01-16 18:21:34 Re: Recalculating OldestXmin in a long-running vacuum
Previous Message Tom Lane 2007-01-16 16:15:26 Re: Enabling autovacuum by default (was Re: Autovacuum improvements)