Re: pgAgent question

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Benjamin Krajmalnik" <kraj(at)illumen(dot)com>, <pgadmin-support(at)postgresql(dot)org>
Subject: Re: pgAgent question
Date: 2006-04-20 20:43:53
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C9E28@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

________________________________

From: Benjamin Krajmalnik [mailto:kraj(at)illumen(dot)com]
Sent: 20 April 2006 20:50
To: Dave Page; pgadmin-support(at)postgresql(dot)org
Subject: RE: [pgadmin-support] pgAgent question


It takes about the same time.
Since I do not need statistics on every single test (some of
them have data that is not suited for statistical analysis), I modified
my schema slightly.
Each test which has to be processed for statistics is tagged as
such, reducing the amount of data processed.

With our current data set it went down to from about 30 seconds
of execution time to about 2 seconds.
Running this new procedure from pgAdmin and psql yielded
approximately the same results (about 2 seconds).

I restarted the pgagent service, and with the new stored
procedure it is taking the same amount of time as with direct calls from
pgadmin or psql.
So, it appears this was somehow a fluke - go figure. I will
monitor this, and if I come across the issue again I will repost.

Yeah - I really can't imagine any reason why it would make any
difference. It's the same client library, running a stored proc wiht
practically zero I/O!! Oh well...


As always, Thanks for your help.

No problem.

Regards, Dave.

Browse pgadmin-support by date

  From Date Subject
Next Message Jan Zach 2006-04-20 21:52:50 query tool save problem
Previous Message Benjamin Krajmalnik 2006-04-20 19:49:59 Re: pgAgent question