Re: Improvement of procArray.xmin for VACUUM

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Improvement of procArray.xmin for VACUUM
Date: 2007-03-27 13:19:40
Message-ID: 200703271319.l2RDJeC03261@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> Uh, no, that's not very clear. A long-running transaction will be a
> >> VACUUM bottleneck because of its own XID, never mind its xmin.
>
> > Well, my secondary addition was to start MyProc->xmin with the current
> > xid counter, rather than your own xid.
>
> Don't tell me you seriously believe that would work.

I do. Please tell me why it will not.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-03-27 13:56:04 Re: patch adding new regexp functions
Previous Message stark 2007-03-27 12:32:04 Patch for circular buffer in tuplestore to optimize merge joins (v1)