I just summarized some of the discussion on this thread and created a
wiki page that starts to cover each of the three tools now available for
this job: http://wiki.postgresql.org/wiki/Statement_Playback
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
Dimitri Fontaine wrote:
Greg Stark gsst...@mit.edu writes:
Do you have a multi-threaded model that tracks which transactions each
query belonged to and runs them concurrently like they were in the
original setup? That's what I've been looking for.
Tsung does that and has been doing it for…
Albe Laurenz laurenz.a...@wien.gv.at writes:
It seems that Tsung currently only supports basic queries, but I
assume that this can be improved.
In fact from the time when PostgreSQL support was added, some more
Erlang drivers have appeared and some of them covers the entire
protocol. So it
Dimitri Fontaine wrote:
One thing that Tsung, recording
queries as proxy, will never be able to handle are encrypted connections,
but I guess that's a minor problem.
Yes, because you typically run the proxy only to record sessions, in
order to prepare the tsung setup. Another way to go
On Mar 23, 2010, at 4:08 AM, Dimitri Fontaine wrote:
One thing that Tsung, recording
queries as proxy, will never be able to handle are encrypted connections,
but I guess that's a minor problem.
Yes, because you typically run the proxy only to record sessions, in
order to prepare the tsung
On Wed, Mar 17, 2010 at 2:06 PM, Albe Laurenz laurenz.a...@wien.gv.at wrote:
I announce the first release of pgreplay, version 0.9.0 (Beta).
Project home page: http://pgreplay.projects.postgresql.org/
pgreplay reads a PostgreSQL log file (*not* a WAL file),
extracts the SQL statements and
Greg Stark gsst...@mit.edu writes:
Do you have a multi-threaded model that tracks which transactions each
query belonged to and runs them concurrently like they were in the
original setup? That's what I've been looking for.
Tsung does that and has been doing it for… quite some time. It even
