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

From Alvaro Herrera
Subject Re: Recalculating OldestXmin in a long-running vacuum
Date
Msg-id 20070313122741.GA4490@alvh.no-ip.org
Whole thread Raw
In response to Re: Recalculating OldestXmin in a long-running vacuum  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: Recalculating OldestXmin in a long-running vacuum
List pgsql-patches
Heikki Linnakangas wrote:

> I ran two 24h test runs with DBT-2, one with the patch and one without.
> To get comparable, predictable results, I turned autovacuum off and run
> a manual vacuum in a loop on the stock-table alone.
>
> As expected, the steady-state of the stock table is smaller with the
> patch. But only by ~2%, that's slightly less than I expected.
>
> But what surprises me is that response times went up a with the patch. I
> don't know why.

Maybe because of increased contention of ProcArrayLock?  (I assume you
are using that, althought I haven't seen the patch)

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-patches by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Recalculating OldestXmin in a long-running vacuum
Next
From: Heikki Linnakangas
Date:
Subject: Re: Recalculating OldestXmin in a long-running vacuum