On Wed, 10 Oct 2007 12:41:49 +0200
Tomáš Vondra <[EMAIL PROTECTED]> wrote:
> Actually we wrote something similar as pgfounie was not as nice as
> today, at that time (2005] - you can find that tool on
> http://opensource.pearshealthcyber.cz/. Actually I'm working on a
> complete rewrite of th
On 10/10/07, Tomáš Vondra <[EMAIL PROTECTED]> wrote:
> Actually we wrote something similar as pgfounie was not as nice as
> today, at that time (2005] - you can find that tool on
> http://opensource.pearshealthcyber.cz/. Actually I'm working on a
> complete rewrite of that tool into Java (new featu
On 10/9/07, Campbell, Lance <[EMAIL PROTECTED]> wrote:
I have noticed a slight spike in the amount of CPU usage in the last few
weeks. I am sure it has to do with a change or two that was made to some
queries. What is the best way to log the SQL that is being executed? I
would prefer to l
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> Campbell, Lance wrote:
>> I have noticed a slight spike in the amount of CPU usage in the last few
>> weeks. I am sure it has to do with a change or two that was made to
>> some queries. What is the best way to log the SQL that is being
>> exec
Campbell, Lance wrote:
> I have noticed a slight spike in the amount of CPU usage in the last few
> weeks. I am sure it has to do with a change or two that was made to
> some queries. What is the best way to log the SQL that is being
> executed?
Take a look at statement_timeout and log_stateme
On 10/9/07, Campbell, Lance <[EMAIL PROTECTED]> wrote:
> I have noticed a slight spike in the amount of CPU usage in the last few
> weeks. I am sure it has to do with a change or two that was made to some
> queries. What is the best way to log the SQL that is being executed? I
> would prefer to
