| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgbench vs. SERIALIZABLE |
| Date: | 2013-05-20 16:28:25 |
| Message-ID: | CAMkU=1wXd_4z+EvJ1fEf7-JNZ+N+FYwckjkv6A3LJqyyDaP-DQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 20, 2013 at 4:50 AM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> I raised this issue near the end of SSI development, but nobody
> seemed very interested and someone argued that a tool to do that
> would be good but we shouldn't try to do it in pgbench -- so I let
> it drop at the time.
>
I think it would be good to do it in pgbench, provided it can be done
fairly cleanly.
Presumably we would want to repeat all of the ordinary commands, in the
file, but not any of the backslash set commands that precede any ordinary
commands. But what if backslash set commands are sprinkled between
ordinary commands?
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-05-20 16:51:25 | Re: Re: pg_basebackup with -R option and start standby have problems with escaped password |
| Previous Message | Heikki Linnakangas | 2013-05-20 16:10:59 | Re: pgbench vs. SERIALIZABLE |