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 from logs is to use > pgfouine, which knows how to prepare a tsung config from PostgreSQL > logs: > > http://pgfouine.projects.postgresql.org/tsung.html
That's nice! > > On the usability side, Tsung will require that all clients are redirected > > to the recording proxy, while pgreplay will only require that the logging > > configuration settings on the server are changed. This can be an advantage > > in large distributed production environments. > > Well never use the tsung recorder in production. Ever. Run it to > construct your sessions files from your application. I see. So that case covers the creation of "artificial" session data as opposed to the above case. Yours, Laurenz Albe -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
