Re: enhanced pgbench

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: enhanced pgbench
Date: 2005-09-28 15:29:56
Message-ID: 20050929.002956.71088630.ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> writes:
> > I think the enhanced pgbench is quite usefull and I would like to
> > include in 8.1. Or should I keep it for 8.2?
>
> Well, we've traditionally been laxer about contrib than the core
> software, so the fact that we're past feature freeze isn't sufficient
> reason to say "no". I'm inclined to say "yes" because I think this
> might make a handy debugging tool --- for instance, Janning Vygen's
> current problem with temp tables might be reproducible using a pgbench
> script, without having to write any new software.

Ok. I will commit patches and will continue to work on below.

> Have you thought about ripping out all the original pgbench code and
> instead having a "default script" that duplicates the original behavior?

No, but seems an idea. There are few things I need to think about:

1) There are three pgbench's default behaviors: TPC-B like(default),
-N and -S. So we need three scripts.

2) it requires a location where those scripts reside. $prefix/etc
seems appropriate?

> Also it seems like it'd be useful if there could be more than one
> script, so as to test situations where the clients aren't all doing
> exactly the same thing.

How do you assign different scripts to different clients?
--
SRA OSS, Inc. Japan
Tatsuo Ishii

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-09-28 15:35:26 Re: [PATCHES] Proposed patch for sequence-renaming problems
Previous Message Bruce Momjian 2005-09-28 15:25:07 Re: [PATCHES] Proposed patch for sequence-renaming problems