Re: pgAgent stats
| От | Marcin Krawczyk |
|---|---|
| Тема | Re: pgAgent stats |
| Дата | |
| Msg-id | 95f6bf9b1003170524i4ae91ea0s9cdc92ccaa41aabf@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pgAgent stats (Dave Page <dpage@pgadmin.org>) |
| Ответы |
Re: pgAgent stats
|
| Список | 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@pgadmin.org>
On Wed, Mar 17, 2010 at 12:15 PM, Marcin Krawczyk <jankes.mk@gmail.com> wrote:Check the 'Maximum number of rows to retrieve' option on the Query tab
> 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 ?
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
В списке pgsql-sql по дате отправления: