From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Dimitri Fontaine *EXTERN*" <dfontaine(at)hi-media(dot)com> |
Cc: | "Greg Stark" <gsstark(at)mit(dot)edu>, "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgreplay log file replayer released |
Date: | 2010-03-23 13:20:49 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C20489C270@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Ben Chobot | 2010-03-23 16:25:49 | [SPAM] Re: pgreplay log file replayer released |
Previous Message | Devrim GÜNDÜZ | 2010-03-23 13:12:02 | 2nd set of PostgreSQL 9.0 Alpha4 RPMs are available. |
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2010-03-23 13:23:58 | Re: Before triggers and usage in partitioned tables |
Previous Message | Sergio Ramazzina | 2010-03-23 12:34:17 | Re: Before triggers and usage in partitioned tables |