Re: [pgsql-patches] Recalculating OldestXmin in a long-running vacuum

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Gregory Stark <gsstark(at)mit(dot)edu>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [pgsql-patches] Recalculating OldestXmin in a long-running vacuum
Date: 2007-02-01 18:40:58
Message-ID: 200702011840.l11Iewn06920@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> > I have two runs of DBT-2, one with the patch and one without.
>
> > Patched:
>
> > autovac "public.stock" scans:1 pages:1285990(-0)
> > tuples:25303056(-2671265) CPU 95.22s/38.02u sec elapsed 10351.17 sec
>
> > Unpatched:
>
> > autovac "public.stock" scans:1 pages:1284504(-0)
> > tuples:25001369(-1973760) CPU 86.55s/34.70u sec elapsed 9628.13 sec
>
> So that makes this patch a good idea why? (Maybe what we need to see
> is the impact on the total elapsed time for the DBT-2 test, rather
> than just the VACUUM runtime.)

Yea, in summary, it looks like the patch made the performance worse.

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

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

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-02-01 19:59:07 Re: Full page writes improvement
Previous Message Bruce Momjian 2007-02-01 18:33:36 Re: [pgsql-patches] Patch to avoid gprofprofilingoverwrites