X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 3CBDE5286E
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Mon, 18 Jul 2005 01:11:16 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 67568-08
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Mon, 18 Jul 2005 04:11:05 +0000 (GMT)
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by svr1.postgresql.org (Postfix) with ESMTP id B25F152AB9
	for <pgsql-performance@postgresql.org>;
	Mon, 18 Jul 2005 01:11:01 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j6I4Arx9024521;
	Mon, 18 Jul 2005 00:10:53 -0400 (EDT)
To: Robert Creager <Robert_Creager@LogicalChaos.org>
Cc: PGPerformance <pgsql-performance@postgresql.org>,
	Andy Hewitt <Andy_Hewitt@StorageTek.com>
Subject: Re: Huge performance problem between 7.4.1 and 8.0.3 - CS issue? 
In-reply-to: <20050717213416.59dcb52e@thunder.logicalchaos.org> 
References: <20050717213416.59dcb52e@thunder.logicalchaos.org>
Comments: In-reply-to Robert Creager <Robert_Creager@LogicalChaos.org>
	message dated "Sun, 17 Jul 2005 21:34:16 -0600"
Date: Mon, 18 Jul 2005 00:10:53 -0400
Message-ID: <24520.1121659853@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL
X-Spam-Level: 
X-Archive-Number: 200507/243
X-Sequence-Number: 13484

Robert Creager <Robert_Creager@LogicalChaos.org> writes:
> I'm guessing this is the CS problem that reared it's head last year?

The context swap problem was no worse in 8.0 than in prior versions,
so that hardly seems like a good explanation.  Have you tried reverting
to the cron-based vacuuming method you used in 7.4?

			regards, tom lane