Re: [HACKERS] Autovacuum loose ends

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Autovacuum loose ends
Date: 2005-08-10 03:58:02
Message-ID: 20050810035802.GA3044@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Tue, Aug 09, 2005 at 11:24:40PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > Hmm. I have a patch for this, but now that it's ready, I wonder if it's
> > really needed. If I understand vacuum_set_xid_limits() correctly, it's
> > very difficult for the vacuumxid to be far behind the freeze limit.
>
> Umm ... they can be close together, or a billion XIDs apart, depending
> on whether the FREEZE option was used.

Sorry, my point was that vacuumxid is generally going to be higher than
freeze-xid, and where it isn't, a simple vacuum can't fix it.

But now that I think about it, maybe the point is that if a long-running
transaction (a billon-transactions old transaction?) was running when
the last database-wide vacuum was run, then vacuumxid is going to be
older than freeze-xid, so we may need a database-wide vacuum to fix that
even though the freeze-xid is not old enough.

Is that right?

--
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
We take risks not to escape from life, but to prevent life escaping from us.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mark 2005-08-10 05:56:57 Re: Simplifying wal_sync_method
Previous Message Tom Lane 2005-08-10 03:24:40 Re: [HACKERS] Autovacuum loose ends

Browse pgsql-patches by date

  From Date Subject
Next Message Luke Lonergan 2005-08-10 04:39:55 Re: COPY FROM performance improvements
Previous Message Tom Lane 2005-08-10 03:24:40 Re: [HACKERS] Autovacuum loose ends