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

From Bruce Momjian
Subject Re: [pgsql-patches] Recalculating OldestXmin in a long-running vacuum
Date
Msg-id 200702011840.l11Iewn06920@momjian.us
Whole thread Raw
In response to Re: [pgsql-patches] Recalculating OldestXmin in a long-running vacuum  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tom Lane wrote:
> Heikki Linnakangas <heikki@enterprisedb.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@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

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

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [pgsql-patches] Patch to avoid gprofprofilingoverwrites
Next
From: Doug Knight
Date:
Subject: Re: pg_standby