Skip site navigation (1) Skip section navigation (2)

Re: pgbench - startup delay

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: pgbench - startup delay
Date: 2007-12-10 22:34:10
Message-ID: 20805.1197326050@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Dave Page <dpage(at)postgresql(dot)org> writes:
> Alvaro Herrera wrote:
>> I think you could get the same effect by putting the -W in PGOPTIONS (in
>> pgbench's environment).

> That's a good point. It does have the downside that it will affect the
> pgbench results - though that wouldn't actually be an issue for what I
> was doing.

Well, if you're attaching a profiler or debugger to a backend, you're
hardly gonna get unadulterated TPS readings from pgbench anyway. 
I concur with Alvaro that this case seems adequately covered by
	PGOPTIONS="-W n" pgbench ...
which is what I've always used in similar situations...

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: Greg SmithDate: 2007-12-11 00:12:07
Subject: Re: pgbench - startup delay
Previous:From: Dave PageDate: 2007-12-10 20:09:55
Subject: Re: pgbench - startup delay

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group