Re: Improvement of procArray.xmin for VACUUM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(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 02:16:31
Message-ID: 10049.1174961791@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

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.

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Jeremy Drake 2007-03-27 02:18:38 Re: patch adding new regexp functions
Previous Message Bruce Momjian 2007-03-27 02:12:39 Re: Improvement of procArray.xmin for VACUUM