Re: pgbench vs. SERIALIZABLE

Поиск
Список
Период
Сортировка
Искать
От
Fabien COELHO
Тема
Re: pgbench vs. SERIALIZABLE
Дата
в 18:16:03
Msg-id
alpine.DEB.2.02.1305201904270.32000@localhost6.localdomain6
Ответ на
Список
Дерево обсуждения
pgbench vs. SERIALIZABLE Josh Berkus <josh@agliodbs.com>
Re: pgbench vs. SERIALIZABLE Kevin Grittner <kgrittn@ymail.com>
Re: pgbench vs. SERIALIZABLE Heikki Linnakangas <hlinnakangas@vmware.com>
Re: pgbench vs. SERIALIZABLE Jeff Janes <jeff.janes@gmail.com>
Re: pgbench vs. SERIALIZABLE Fabien COELHO <coelho@cri.ensmp.fr>
Re: pgbench vs. SERIALIZABLE Fabien COELHO <coelho@cri.ensmp.fr>
Re: pgbench vs. SERIALIZABLE Marko Tiikkaja <marko@joh.to>
Re: pgbench vs. SERIALIZABLE Fabien COELHO <coelho@cri.ensmp.fr>

> 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


В списке pgsql-hackers по дате отправления
От: Heikki Linnakangas
Дата:
Сообщение: Re: Fast promotion failure
От: Heikki Linnakangas
Дата:
FAQ