On Thu, Aug 27, 2009 at 09:38:15PM +0200, Dimitri Fontaine wrote: > Exactly, and I think that what we're missing here is a simple tool for > our users to check a new PostgreSQL release against their existing > application. > > We already know how to either log all queries and analyze the log files > (CSV makes it easier, pgfouine parses them too) or to have a fe/be > protocol proxy to record application SQL traffic (tsung recorder does > that). > > What we miss is a tool to run the captured queries through both versions > of PG and report any resultset mismatch, of course with a way to account > for ordering issues (but we've seen people rely on the ordering when > they don't give an order by clause, then bug the lists about it if a new > release changes it).
This would be very useful. I often am asked "how much better will the new release run our apps" as part of convincing a client to upgrade to a more current postgresql release. Being able to replay a days workload in a somewhat realistic manner would be a great help. -dg -- David Gould da...@sonic.net 510 536 1443 510 282 0869 If simplicity worked, the world would be overrun with insects. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
