From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, <robertmhaas(at)gmail(dot)com>, <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: commit fests |
Date: | 2010-01-24 19:38:28 |
Message-ID: | m2k4v7z423.fsf@hi-media.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>> As for getting more coverage of Beta, part of my trouble in
>> testing applications on Beta is that there aren't good tools I
>> know of for capture and replay of usage scenarios. Now there would
>> be a good project for someone, and it would be unaffected by the
>> Beta cycle.
>
> Did you follow any of the dtester discussion? That would allow
> replay of complex usage scenarios, although they would be scripted,
> rather than captured. Would that help any?
And there's already pgfouine to get the scenarios from the logs and
tsung to act as a recording proxy:
http://pgfouine.projects.postgresql.org/tsung.html
http://tsung.erlang-projects.org/user_manual.html#htoc34
So maybe it would be a good idea to have dtester able to replay a tsung
session file so that we already know how to get this input?
Then dtester would be for validating queries output and tsung for
testing the scalability, both working with the same format.
Regards,
--
dim
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-01-24 19:45:10 | Re: 8.5 vs. 9.0, Postgres vs. PostgreSQL |
Previous Message | Peter Eisentraut | 2010-01-24 19:32:16 | Re: tab completion for prepared transactions? |