Re: Query preformence - Mailing list pgsql-patches

From Ferdinand Smit
Subject Re: Query preformence
Date
Msg-id 200111080947.fA89lFd13455@server9.telegraafnet.nl
Whole thread Raw
In response to Re: Query preformence  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Query preformence  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Hi Tom,

> > In postgres there is no relationship between de debug_print_query and the
> > show_query_stats, so you can't monitor the query preformance.
>
> What?  This seems completely redundant with the existing logging tools.

True, but i can't see any usable function for the statics because they are
logged without any relation. You don't know what is causing the preformence
problem. We want to monitor the duration of query's so we can create smart
indexed and smart query's. With postgres this is imposible at the moment.

In the progres the debug is only for logging and the statics only for
statics, so you always have redundant code if don't want to change the whole
code.

But, do you have a better idea?

Ferdinand Smit

Yes, i'm a newbe so i choose a simple solution without disturbing any code ;-)

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fix for 'extern "C"' indenting
Next
From: Marko Kreen
Date:
Subject: pgcrypto bug