From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] pgbench: new feature allowing to launch shell commands |
Date: | 2009-08-07 04:20:41 |
Message-ID: | c64c5f8b0908062120p6bab95e2saba3dabe3e895532@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Yes it dramatically decreases the transaction flow.
This function has not been implemented at all for performance but for
analysis purposes.
I used it mainly to have a look at state files size in pg_twophase for
transactions that are prepared but not committed.
Regards
On Fri, Aug 7, 2009 at 12:55 PM, Itagaki Takahiro <
itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> wrote:
>
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
>
> > > Here is a short patch implementing a new feature in pgbench so as to
> allow
> > > shell commands to be launched in a transaction file of pgbench.
> > > \shell ls ~/pg_twophase;
>
> +1 for \shell command itself, but does the performance fit for your
> purpose?
> Spawning a new process is not so cheap, no?
>
> -1 for -P option because it is too narrow purpose and 'ls' and '/tmp/'
> is not portable. We don't need to include your workload because you can
> use -f FILENAME to run your benchmark script.
>
> Regards,
> ---
> ITAGAKI Takahiro
> NTT Open Source Software Center
>
>
>
--
Michael Paquier
NTT OSSC
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-08-07 04:26:47 | Re: Fwd: [BUGS] fix: plpgsql: return query and dropped columns problem |
Previous Message | Alvaro Herrera | 2009-08-07 03:59:50 | Re: [PATCH] pgbench: new feature allowing to launch shell commands |