Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 50AF1797DB8 for ; Wed, 17 Mar 2010 09:16:21 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 74925-06 for ; Wed, 17 Mar 2010 12:16:03 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f220.google.com (mail-ew0-f220.google.com [209.85.219.220]) by mail.postgresql.org (Postfix) with ESMTP id 64ACB797C8C for ; Wed, 17 Mar 2010 09:16:10 -0300 (ADT) Received: by ewy20 with SMTP id 20so413179ewy.21 for ; Wed, 17 Mar 2010 05:16:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=rkepoehl6SCO8Whxt2dVzdIH6Afraq5X70Cw/SPWH2E=; b=vrZ2lQdlqq/+H+OF5G1m1J61su8zqjrpHBHrK0gRYMLaA/KpMfaBjl4TZHG2rUqgTG yzqt4zo3BEQKOgXeV79kKsbeWKjl100YVWZUtyYipsH52Ld/N1tKnHoIqg8Mj5dQAHjo h4P94ftkLvmZJN4Rj7uW1BySevDaq6vvouIvk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=Tv6KqYL2U6ehCbo2ITOkYJoZWCe2HLG+emVjzFg/gaOhStnFu3wTTSQ/fpUSsE/Mxz dWpIq913nApAKOEEUrbEaGCCdy3PeilZxrWE9QQULf/bUTJYXL+dfegtWio/UUNqQP2V dcwtEGBZkvNComg5gxWYP/JCV49VShTtERZpo= MIME-Version: 1.0 Received: by 10.213.38.203 with SMTP id c11mr621071ebe.43.1268828165123; Wed, 17 Mar 2010 05:16:05 -0700 (PDT) In-Reply-To: <4BA0C4EF.9000603@lelarge.info> References: <95f6bf9b1003160040u3e658e3cg486a614cdd284a52@mail.gmail.com> <4BA0C4EF.9000603@lelarge.info> From: Marcin Krawczyk Date: Wed, 17 Mar 2010 13:15:45 +0100 Message-ID: <95f6bf9b1003170515u4d80ad9dgd80ef3ee1bb20771@mail.gmail.com> Subject: Re: pgAgent stats To: Guillaume Lelarge Cc: pgsql-sql@postgresql.org Content-Type: multipart/alternative; boundary=00163600d6871042b30481fe1428 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.598 tagged_above=-10 required=5 tests=BAYES_00=-2.599, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201003/125 X-Sequence-Number: 33832 --00163600d6871042b30481fe1428 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable It's pgAdmin 1.10.0. I've partially identified the problem, pgAdmin log say= s that following query gets executed when switching to job statistics tab : SELECT jsljlgid, jslstatus, jslresult, jslstart, jslduration, (jslstart + jslduration) AS endtime, jsloutput FROM pgagent.pga_jobsteplog WHERE jsljstid =3D 5 ORDER BY jslstart DESC LIM= IT 0 obviously the problem is LIMIT 0 clause but why it is there remains a mystery... pgAdmin bug ? a configuration issue ? regards mk 2010/3/17 Guillaume Lelarge > Hi, > > Le 16/03/2010 08:40, Marcin Krawczyk a =E9crit : > > Hi list, does anyone know the reason for pgAdmin not showing the stats > > neither for selected pgAgent step nor whole job ? The pga_joblog and > > pga_jobsteplog both get populated with data on run so I was thinking th= at > > maybe I'm missing some view associated with statistics tabs ?? Any idea= s > ? > > > > Which release of pgAdmin? > > AFAICT, 1.10 Jobs' and Steps' statistics are last run time, status, > start time, stop time, and duration. > > > -- > Guillaume. > http://www.postgresqlfr.org > http://dalibo.com > --00163600d6871042b30481fe1428 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
It's pgAdmin 1.10.0. I've partially identified the problem, pg= Admin log says that following query gets executed when=A0switching=A0to job= =A0statistics=A0tab :

SELECT jsljlgid, jslsta= tus, jslresult, jslstart, jslduration, (jslstart + jslduration) AS endtime,= jsloutput =A0
FROM pgagent.pga_jobsteplog=A0WHERE jsljstid =3D 5 ORDER BY jslstart D= ESC LIMIT 0

obviously the problem is LIMIT 0= clause but why it is there remains a=A0mystery... pgAdmin bug ? a configur= ation issue ?


regards
mk


2010/3/17 Guillaume Lelarge <guill= aume@lelarge.info>
Hi,

Le 16/03/2010 08:40, Marcin Krawczyk a =E9crit :
> Hi list, does anyone know the reason for pgAdmin = not showing the stats
> neither for selected pgAgent step nor whole job ? The pga_joblog and > pga_jobsteplog both get populated with data on run so I was thinking t= hat
> maybe I'm missing some view associated with statistics tabs ?? Any= ideas ?
>

Which release of pgAdmin?

AFAICT, 1.10 Jobs' and Steps' statistics are last run time, status,=
start time, stop time, and duration.


--
Guillaume.
=A0http://www.pos= tgresqlfr.org
=A0http://dalibo.com

--00163600d6871042b30481fe1428--