> > If anyone is interested, let me know and I'll add this to my ToDo
> > list.
>
> The Sun benchmarking team needs this. However, we need to be able to feed
> the data into some kind of mass analysis ala pg_fouine so that we can do
> overall performance analysis.
I've also included a PL/pgSQ
Korry,
> If anyone is interested, let me know and I'll add this to my ToDo
> list.
The Sun benchmarking team needs this. However, we need to be able to feed
the data into some kind of mass analysis ala pg_fouine so that we can do
overall performance analysis.
--
--Josh
Josh Berkus
PostgreSQ
> Josh Berkus writes:
> > In recent versions, we've changed the logging of function executions so
> > that only the function call is logged, and not any of the queries which it
> > may execute internally. While most of the time this method is superior
> > for performance analysis, in applicati
Josh Berkus writes:
> In recent versions, we've changed the logging of function executions so
> that only the function call is logged, and not any of the queries which it
> may execute internally. While most of the time this method is superior
> for performance analysis, in applications with e
Hackers,
> In recent versions, we've changed the logging of function executions so
> that only the function call is logged, and not any of the queries which
> it may execute internally. While most of the time this method is
> superior for performance analysis, in applications with extensive
> mul
Hackers,
In recent versions, we've changed the logging of function executions so
that only the function call is logged, and not any of the queries which it
may execute internally. While most of the time this method is superior
for performance analysis, in applications with extensive multi-line
