| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, 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 18:15:49 |
| Message-ID: | alpine.DEB.2.02.1305201904270.32000@localhost6.localdomain6 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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?
As I have spent some time in pgbench recently, ISTM that when restarting
the transaction (reset state = 0), you want to keep track of the farthest
state that was reached on previous attempts, so as to skip backslash
commands for those states, and restart execute them where they were left.
That would mean one integer for this purpose in the client structure.
--
Fabien
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-05-20 19:06:20 | Re: fast promotion and log_checkpoints |
| Previous Message | Heikki Linnakangas | 2013-05-20 17:47:06 | Re: Fast promotion failure |