Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id E504279957D for ; Wed, 17 Mar 2010 09:43:16 -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 78629-05 for ; Wed, 17 Mar 2010 12:42:57 +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 3125B79930E for ; Wed, 17 Mar 2010 09:43:05 -0300 (ADT) Received: by wyb38 with SMTP id 38so482646wyb.19 for ; Wed, 17 Mar 2010 05:43:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.93.1 with SMTP id k1mr462503wef.151.1268829782754; Wed, 17 Mar 2010 05:43:02 -0700 (PDT) In-Reply-To: <95f6bf9b1003170540u5941c483vedba4a92337f15ac@mail.gmail.com> References: <95f6bf9b1003160040u3e658e3cg486a614cdd284a52@mail.gmail.com> <4BA0C4EF.9000603@lelarge.info> <95f6bf9b1003170515u4d80ad9dgd80ef3ee1bb20771@mail.gmail.com> <937d27e11003170519y1cc72ff8nab65804fab01e422@mail.gmail.com> <95f6bf9b1003170524i4ae91ea0s9cdc92ccaa41aabf@mail.gmail.com> <937d27e11003170528p7fb666fvf2e6e28eda7082c2@mail.gmail.com> <95f6bf9b1003170540u5941c483vedba4a92337f15ac@mail.gmail.com> Date: Wed, 17 Mar 2010 12:43:02 +0000 Message-ID: <937d27e11003170543h3bd6d4ddl8016fdbc0c9101fa@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 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.449 tagged_above=-10 required=5 tests=AWL=0.150, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/132 X-Sequence-Number: 33839 :-) On Wed, Mar 17, 2010 at 12:40 PM, Marcin Krawczyk wrote: > Yeah... my bad. Sorry for being a pain in the a... ;) > > pozdrowienia > mk > > > 2010/3/17 Dave Page >> >> On Wed, Mar 17, 2010 at 12:24 PM, Marcin Krawczyk >> wrote: >> > Ha, it worked :)) kind of funny though. It was set to 0 but it's >> > supposed to >> > not limit anything when 0 :)) a bug ? >> >> What makes you say that? The docs say: >> >> Maximum rows to retrieve - This option specifies the number of job and >> job step statistics rows to retrieve when viewing the statistics in >> the main browser. Unlike the statistics for other objects which >> normally consist of a fixed number of rows, a row is created every >> time a job or job step is executed. The most recent statistics will be >> shown. >> >> >> -- >> Dave Page >> EnterpriseDB UK: http://www.enterprisedb.com >> PG East Conference: >> http://www.enterprisedb.com/community/nav-pg-east-2010.do > > -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com PG East Conference: http://www.enterprisedb.com/community/nav-pg-east-2010.do