DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender;
	b=TiIbJesdIxM9Rxqw/yIfTQC4Jz4/1qRYESc6gKZX01jx9JbvnuauRJA24YHEKdhEXqSf3q8jEaDmn6jyhoiOSZXpv0jYwvjH9W8TXtTNminyY6HyobSzfm5S1VcPnm15pomrW92AWbAuVGo63XtrlTBmeevNqzRbjnpQeMHLzhQ=
Message-ID: <4664748B.2060304@enterprisedb.com>
Date: Mon, 04 Jun 2007 21:22:35 +0100
From: Heikki Linnakangas <heikki@enterprisedb.com>
User-Agent: Icedove 1.5.0.10 (X11/20070329)
MIME-Version: 1.0
To: Markus Schiltknecht <markus@bluegap.ch>
CC: pgsql-performance@postgresql.org
Subject: Re: dbt2 NOTPM numbers
References: <466428F7.5010808@bluegap.ch> <46642B33.6030101@enterprisedb.com>
	<46642F2E.3080509@bluegap.ch>
In-Reply-To: <46642F2E.3080509@bluegap.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Markus Schiltknecht wrote:
> Hi,
> 
> Heikki Linnakangas wrote:
>> There's clearly something wrong. The response times are ridiculously 
>> high, they should be < 5 seconds (except for stock level transaction) 
>> to pass a TPC-C test. I wonder if you built any indexes at all?
> 
> Hm.. according to the output/5/db/plan0.out, all queries use index 
> scans, so that doesn't seem to be the problem.

I still suspect there's something wrong with plans, I doubt you can get 
that bad performance unless it's doing something really stupid. I'd 
suggest setting log_min_duration_statement = 5000, and seeing what you 
get. Also check pg_stat_user_table.seq_scan just to be extra sure 
there's no seq scans.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com