Technically you can then use pgbench on that set of statements, but I usually just use perl's "Benchmark" module.... (i'm sure ruby or java or whatever has a similar tool)
(First, I log statements by loading the application or web server with statement logging turned on.... so I'm not "guessing" what sql will be called. Usually doing this exposes a flotilla of inefficencies in the code ....) On Tue, Jun 9, 2009 at 9:53 AM, Tom Lane<t...@sss.pgh.pa.us> wrote: > Shaul Dar <shaul...@gmail.com> writes: >> Have you actually run pgbench against your own schema? Can you point me to >> an example? I also had the same impression reading the documentation. But >> when I tried it with the proper flags to use my own DB and query file I got >> an error that it couldn't find one of the tables mentioned in the built-in >> test! I concluded that I cannot use any schema, > > No, you just need to read the documentation. There's a switch that > prevents the default action of trying to vacuum the "standard" tables. > I think -N, but too lazy to look ... > > regards, tom lane > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
