Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 6E7BC797DB8 for ; Wed, 17 Mar 2010 09:19: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 75399-02 for ; Wed, 17 Mar 2010 12:19:03 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-wy0-f174.google.com (mail-wy0-f174.google.com [74.125.82.174]) by mail.postgresql.org (Postfix) with ESMTP id 64D2A797C8C for ; Wed, 17 Mar 2010 09:19:10 -0300 (ADT) Received: by wyb38 with SMTP id 38so472423wyb.19 for ; Wed, 17 Mar 2010 05:19:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.85.140 with SMTP id u12mr18757wee.78.1268828347787; Wed, 17 Mar 2010 05:19:07 -0700 (PDT) In-Reply-To: <95f6bf9b1003170515u4d80ad9dgd80ef3ee1bb20771@mail.gmail.com> References: <95f6bf9b1003160040u3e658e3cg486a614cdd284a52@mail.gmail.com> <4BA0C4EF.9000603@lelarge.info> <95f6bf9b1003170515u4d80ad9dgd80ef3ee1bb20771@mail.gmail.com> Date: Wed, 17 Mar 2010 12:19:07 +0000 Message-ID: <937d27e11003170519y1cc72ff8nab65804fab01e422@mail.gmail.com> Subject: Re: pgAgent stats From: Dave Page To: Marcin Krawczyk Cc: Guillaume Lelarge , pgsql-sql@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.447 tagged_above=-10 required=5 tests=AWL=0.152, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/126 X-Sequence-Number: 33833 On Wed, Mar 17, 2010 at 12:15 PM, Marcin Krawczyk wro= te: > It's pgAdmin 1.10.0. I've partially identified the problem, pgAdmin log s= ays > that following query gets executed when=A0switching=A0to job=A0statistics= =A0tab : > SELECT jsljlgid, jslstatus, jslresult, jslstart, jslduration, (jslstart + > jslduration) AS endtime, jsloutput > FROM pgagent.pga_jobsteplog=A0WHERE jsljstid =3D 5 ORDER BY jslstart DESC= LIMIT > 0 > obviously the problem is LIMIT 0 clause but why it is there remains > a=A0mystery... pgAdmin bug ? a configuration issue ? Check the 'Maximum number of rows to retrieve' option on the Query tab of the Options dialog. --=20 Dave Page EnterpriseDB UK: http://www.enterprisedb.com PG East Conference: http://www.enterprisedb.com/community/nav-pg-east-2010.= do