| From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: multi-threaded pgbench |
| Date: | 2009-07-09 04:08:17 |
| Message-ID: | alpine.GSO.2.01.0907090006350.11767@westnet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 8 Jul 2009, Tom Lane wrote:
> pg_restore doesn't need anything more than a success/failure result
> from its child processes, but I think pgbench will want more.
The biggest chunk of returned state to consider is how each client
transaction generates a line of latency information that goes into the log
file.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2009-07-09 06:08:43 | Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby |
| Previous Message | Tom Lane | 2009-07-09 04:06:29 | Re: *_collapse_limit, geqo_threshold |