Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 23640632820 for ; Sat, 1 May 2010 14:16:03 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 11288-08 for ; Sat, 1 May 2010 17:15:55 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.illumen.com (unknown [64.207.29.137]) by mail.postgresql.org (Postfix) with ESMTP id ACDB9632582 for ; Sat, 1 May 2010 14:15:55 -0300 (ADT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: Autovacuum stopped running Date: Sat, 1 May 2010 11:15:53 -0600 Message-ID: In-Reply-To: <4BDBF3C90200002500031147@gw.wicourts.gov> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] Autovacuum stopped running Thread-Index: AcrpOk5vxnu/TZOpScqEYJ6MLQWOOQAFzhHw References: <4BDBF3C90200002500031147@gw.wicourts.gov> From: "Benjamin Krajmalnik" To: "Kevin Grittner" , X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.107 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RDNS_NONE=0.793 X-Spam-Level: X-Archive-Number: 201005/3 X-Sequence-Number: 34476 TO be truthful, I did not check that. I arrived at the conclusion because although I have 10 autovacuum threads, none of the tables had been autoanalyzed or autovacuumed in hours (and due to the nature of the activity they do so every minute). If I ever see this behavior now I know what to check for :) Thx. > -----Original Message----- > From: Kevin Grittner [mailto:Kevin.Grittner@wicourts.gov] > Sent: Saturday, May 01, 2010 8:27 AM > To: Benjamin Krajmalnik; pgsql-admin@postgresql.org > Subject: Re: [ADMIN] Autovacuum stopped running >=20 > "Benjamin Krajmalnik" wrote: > > I had a very strange occurrence 2 days ago where autovacuum > > appears to have stopped running. >=20 > What did you see which led you to that conclusion? Did ps show the > 'autovacuum launcher process'? >=20 > > I did not see any error messages in pg_log. The problem caused a > > file which is usually around 50Mb but which gets updated > > extensively to grow to 105GB, which in turn brought the server's > > performance down to unusable levels. >=20 > Were there any long-running transactions showing in > pg_stat_activity? (That would include transactions showing ' > in transaction'.) >=20 > -Kevin