From: | Marcin Krawczyk <jankes(dot)mk(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: pgAgent stats |
Date: | 2010-03-17 12:24:17 |
Message-ID: | 95f6bf9b1003170524i4ae91ea0s9cdc92ccaa41aabf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)pgadmin(dot)org>
> On Wed, Mar 17, 2010 at 12:15 PM, Marcin Krawczyk <jankes(dot)mk(at)gmail(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Arnab Ghosh | 2010-03-17 12:25:14 | Postgresql format for ISO8601 |
Previous Message | Dave Page | 2010-03-17 12:19:07 | Re: pgAgent stats |