Received: from localhost (maia-3.hub.org [200.46.204.184])
	by postgresql.org (Postfix) with ESMTP id 6CAF19FA248
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Tue, 12 Dec 2006 13:14:16 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024)
	with ESMTP id 00994-06 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Tue, 12 Dec 2006 13:14:01 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id 55B899FA162
	for <pgsql-performance@postgresql.org>;
	Tue, 12 Dec 2006 13:14:02 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kBCHDxgr004776;
	Tue, 12 Dec 2006 12:13:59 -0500 (EST)
To: Alvaro Herrera <alvherre@commandprompt.com>
cc: Alexander Staubo <alex@purefiction.net>,
	Michael Stone <mstone+postgres@mathom.us>, pgsql-performance@postgresql.org
Subject: Re: New to PostgreSQL, performance considerations 
In-reply-to: <20061212161106.GF22782@alvh.no-ip.org> 
References: <20061211173105.GH16692@mathom.us>
	<E1Gtplp-0004Ka-GM@elasmtp-junco.atl.sa.earthlink.net>
	<20061211184726.GI16692@mathom.us>
	<E1GtrB8-0005rw-Iu@elasmtp-kukur.atl.sa.earthlink.net>
	<457DA782.3060506@modgraph-usa.com>
	<8a0c7af10612111422x6bdcc0c2p7cbfeb5a7b0e0374@mail.gmail.com>
	<2FC0D8E7-F8ED-452F-BB13-FB665B516E7F@purefiction.net>
	<20061212123252.GR16692@mathom.us>
	<42B14BCF-B745-4F94-B5EA-97997744A4D5@purefiction.net>
	<3356.1165938462@sss.pgh.pa.us>
	<20061212161106.GF22782@alvh.no-ip.org>
Comments: In-reply-to Alvaro Herrera <alvherre@commandprompt.com>
	message dated "Tue, 12 Dec 2006 13:11:06 -0300"
Date: Tue, 12 Dec 2006 12:13:59 -0500
Message-ID: <4775.1165943639@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200612/304
X-Sequence-Number: 22360

Alvaro Herrera <alvherre@commandprompt.com> writes:
> While skimming over the pgbench source it has looked to me like it's
> necessary to pass the -s switch (scale factor) to both the
> initialization (-i) and the subsequent (non -i) runs.

No, it's not supposed to be, and I've never found it needed in practice.
The code seems able to pull the scale out of the database (I forget how
it figures it out exactly).

			regards, tom lane