Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id D3CB8799314
	for <pgsql-sql-postgresql.org@mail.postgresql.org>;
	Wed, 17 Mar 2010 09:24:51 -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 75813-08 for
	<pgsql-sql-postgresql.org@mail.postgresql.org>;
	Wed, 17 Mar 2010 12:24:33 +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 A9604797C8C
	for <pgsql-sql@postgresql.org>; Wed, 17 Mar 2010 09:24:40 -0300 (ADT)
Received: by ewy20 with SMTP id 20so416248ewy.21
	for <pgsql-sql@postgresql.org>; Wed, 17 Mar 2010 05:24:38 -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=B4zhvJzfp6O4TKiVZdsf8NvzMLn9/JNlczH1T9fEXco=;
	b=TWsqm9L7kTj0PAFBSwzV6P0agFbTVGITBLHc+9FIEI0ZUrVSFaueQN84D2p4co59wG
	aaEdpTXVzNaxNXdwlWu5RAYOZ/VxCP7lAaSc2hJYn9k74WaKsHzv9oeM/qygvP1bgiEN
	LSuuGP8ubq3Um4QeYwY01D7HWQh0DvLRXoaa8=
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=nHED0GFpCDzZz/XSYkkMpG+58PYeAtiIquucVnZcSFtutnpOOgQHeuTIkEmx2K60Ke
	Ig8u1xCXTBVvrOG9UC/2b1RODpoMNolqu4OIFfxo/YCBcvKdkr5xiCZl5Kon+Nhi/IVv
	eRSxiO2SGGXLECquD/wYVwY/xO/UiY5vxwW1E=
MIME-Version: 1.0
Received: by 10.213.109.205 with SMTP id k13mr6712142ebp.44.1268828677417;
	Wed, 17 Mar 2010 05:24:37 -0700 (PDT)
In-Reply-To: <937d27e11003170519y1cc72ff8nab65804fab01e422@mail.gmail.com>
References: <95f6bf9b1003160040u3e658e3cg486a614cdd284a52@mail.gmail.com>
	<4BA0C4EF.9000603@lelarge.info>
	<95f6bf9b1003170515u4d80ad9dgd80ef3ee1bb20771@mail.gmail.com>
	<937d27e11003170519y1cc72ff8nab65804fab01e422@mail.gmail.com>
From: Marcin Krawczyk <jankes.mk@gmail.com>
Date: Wed, 17 Mar 2010 13:24:17 +0100
Message-ID: <95f6bf9b1003170524i4ae91ea0s9cdc92ccaa41aabf@mail.gmail.com>
Subject: Re: pgAgent stats
To: Dave Page <dpage@pgadmin.org>
Cc: Guillaume Lelarge <guillaume@lelarge.info>, pgsql-sql@postgresql.org
Content-Type: multipart/alternative; boundary=000e0ce0d7e4992f1c0481fe3225
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/127
X-Sequence-Number: 33834

--000e0ce0d7e4992f1c0481fe3225
Content-Type: text/plain; charset=ISO-8859-1

Ha, it worked :)) kind of funny though. It was set to 0 but it's supposed to
not limit anything when 0 :)) a bug ?


pozdrowienia / regards / salutations
mk


2010/3/17 Dave Page <dpage@pgadmin.org>

> On Wed, Mar 17, 2010 at 12:15 PM, Marcin Krawczyk <jankes.mk@gmail.com>
> wrote:
> > It's pgAdmin 1.10.0. I've partially identified the problem, pgAdmin log
> says
> > 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 = 5 ORDER BY jslstart DESC
> LIMIT
> > 0
> > obviously the problem is LIMIT 0 clause but why it is there remains
> > a mystery... pgAdmin bug ? a configuration issue ?
>
> Check the 'Maximum number of rows to retrieve' option on the Query tab
> of the Options dialog.
>
>
>
> --
> Dave Page
> EnterpriseDB UK: http://www.enterprisedb.com
> PG East Conference:
> http://www.enterprisedb.com/community/nav-pg-east-2010.do
>

--000e0ce0d7e4992f1c0481fe3225
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Ha, it worked :)) kind of funny though. It was set to 0 but it&#39;s s=
upposed to not limit anything when 0 :)) a bug ?</div><div><br></div><br cl=
ear=3D"all">pozdrowienia / regards / salutations<br>mk<br>
<br><br><div class=3D"gmail_quote">2010/3/17 Dave Page <span dir=3D"ltr">&l=
t;<a href=3D"mailto:dpage@pgadmin.org">dpage@pgadmin.org</a>&gt;</span><br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">

<div class=3D"im">On Wed, Mar 17, 2010 at 12:15 PM, Marcin Krawczyk &lt;<a =
href=3D"http://jankes.mk" target=3D"_blank">jankes.mk</a>@<a href=3D"http:/=
/gmail.com" target=3D"_blank">gmail.com</a>&gt; wrote:<br>
&gt; It&#39;s pgAdmin 1.10.0. I&#39;ve partially identified the problem, pg=
Admin log says<br>
&gt; that following query gets executed when=A0switching=A0to job=A0statist=
ics=A0tab :<br>
&gt; SELECT jsljlgid, jslstatus, jslresult, jslstart, jslduration, (jslstar=
t +<br>
&gt; jslduration) AS endtime, jsloutput<br>
&gt; FROM pgagent.pga_jobsteplog=A0WHERE jsljstid =3D 5 ORDER BY jslstart D=
ESC LIMIT<br>
&gt; 0<br>
&gt; obviously the problem is LIMIT 0 clause but why it is there remains<br=
>
&gt; a=A0mystery... pgAdmin bug ? a configuration issue ?<br>
<br>
</div>Check the &#39;Maximum number of rows to retrieve&#39; option on the =
Query tab<br>
of the Options dialog.<br>
<font color=3D"#888888"><br>
<br>
<br>
--<br>
Dave Page<br>
EnterpriseDB UK: <a href=3D"http://www.enterprisedb.com" target=3D"_blank">=
http://www.enterprisedb.com</a><br>
PG East Conference: <a href=3D"http://www.enterprisedb.com/community/nav-pg=
-east-2010.do" target=3D"_blank">http://www.enterprisedb.com/community/nav-=
pg-east-2010.do</a><br>
</font></blockquote></div><br>

--000e0ce0d7e4992f1c0481fe3225--