From: Dave Page <dpage@pgadmin.org>
To: Marcin Krawczyk <jankes.mk@gmail.com>
Cc: Guillaume Lelarge <guillaume@lelarge.info>
Cc: pgsql-sql@postgresql.org
Subject: Re: pgAgent stats
Date: Wed, 17 Mar 2010 12:19:07 +0000
Message-ID: <937d27e11003170519y1cc72ff8nab65804fab01e422@mail.gmail.com> (raw)
In-Reply-To: <95f6bf9b1003170515u4d80ad9dgd80ef3ee1bb20771@mail.gmail.com>
References: <95f6bf9b1003160040u3e658e3cg486a614cdd284a52@mail.gmail.com>
<4BA0C4EF.9000603@lelarge.info>
<95f6bf9b1003170515u4d80ad9dgd80ef3ee1bb20771@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: dpage@pgadmin.org, jankes.mk@gmail.com, guillaume@lelarge.info
Subject: Re: pgAgent stats
In-Reply-To: <937d27e11003170519y1cc72ff8nab65804fab01e422@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox