From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | <pgsql-announce(at)postgresql(dot)org> |
Subject: | pgreplay log file replayer released |
Date: | 2010-03-17 14:06:20 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C20489C252@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-general |
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 executes them in the same order
and relative time against a PostgreSQL database cluster.
If the execution of statements gets behind schedule, warning
messages are issued that indicate that the server cannot handle
the load in a timely fashion.
The idea is to replay a real-world database workload as exactly
as possible.
pgreplay is useful for performance tests, particularly in the
following situations:
* You want to compare the performance of your PostgreSQL
application on different hardware or different operating systems.
* You want to upgrade your database and want to make sure that
the new database version does not suffer from performance
regressions that affect you.
Features:
* Should compile and run on any platform that PostgreSQL supports
* Can replay the workload at different speeds
* Can parse "stderr" and "csvlog" log files
* Can save workload to replay in "replay file" for reuse
Enjoy!
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2010-03-21 23:17:50 | == PostgreSQL Weekly News - March 21 2010 == |
Previous Message | Devrim GÜNDÜZ | 2010-03-16 12:01:48 | Announcing new PostgreSQL RPM Repository |
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Barwick | 2010-03-17 14:11:40 | Re: Unexpected result from selecting an aliased but non-existing column called "name" |
Previous Message | Vick Khera | 2010-03-17 14:04:13 | Re: app table names |