Received: from maia.hub.org (maia-1.hub.org [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 042EC632700 for ; Mon, 3 May 2010 00:17:14 -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 61738-06 for ; Mon, 3 May 2010 03:17:06 +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 276DA632614 for ; Mon, 3 May 2010 00:17:05 -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: Sun, 2 May 2010 21:17:04 -0600 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] Autovacuum stopped running Thread-Index: Acrpg18KZqAQO+awQqS0CKgBMLu+pQAASY5wADoPhVA= References: <4BDBF3C90200002500031147@gw.wicourts.gov> <11024.1272755375@sss.pgh.pa.us> From: "Benjamin Krajmalnik" To: "Tom Lane" Cc: 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/13 X-Sequence-Number: 34486 OK. This happened again on another server with these same settings. I did not see any long running transaction, and the autovacuum launch process was running. > -----Original Message----- > From: Benjamin Krajmalnik > Sent: Saturday, May 01, 2010 5:22 PM > To: 'Tom Lane' > Cc: Kevin Grittner; pgsql-admin@postgresql.org > Subject: RE: [ADMIN] Autovacuum stopped running >=20 > # - Cost-Based Vacuum Delay - >=20 > #vacuum_cost_delay =3D 0ms # 0-100 milliseconds > #vacuum_cost_page_hit =3D 1 # 0-10000 credits > #vacuum_cost_page_miss =3D 10 # 0-10000 credits > #vacuum_cost_page_dirty =3D 20 # 0-10000 credits > vacuum_cost_limit =3D 10000 # 1-10000 credits >=20 > #---------------------------------------------------------------------- > -------- > # AUTOVACUUM PARAMETERS > #---------------------------------------------------------------------- > -------- >=20 > #autovacuum =3D on # Enable autovacuum subprocess? 'on' > # requires track_counts to also be on. > #log_autovacuum_min_duration =3D -1 # -1 disables, 0 logs all actions > and > # their durations, > 0 logs only > # actions running at least this number > # of milliseconds. > autovacuum_max_workers =3D 10 # max number of autovacuum > subprocesses > #autovacuum_naptime =3D 1min # time between autovacuum runs > #autovacuum_vacuum_threshold =3D 50 # min number of row updates before > # vacuum > #autovacuum_analyze_threshold =3D 50 # min number of row updates before > # analyze > #autovacuum_vacuum_scale_factor =3D 0.2 # fraction of table size > before vacuum > #autovacuum_analyze_scale_factor =3D 0.1 # fraction of table size > before analyze > #autovacuum_freeze_max_age =3D 200000000 # maximum XID age before > forced vacuum > # (change requires restart) > #autovacuum_vacuum_cost_delay =3D 20ms # default vacuum cost delay > for > # autovacuum, in milliseconds; > # -1 means use vacuum_cost_delay > #autovacuum_vacuum_cost_limit =3D -1 # default vacuum cost limit for > # autovacuum, -1 means use > # vacuum_cost_limit >=20 >=20 > > -----Original Message----- > > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > > Sent: Saturday, May 01, 2010 5:10 PM > > To: Benjamin Krajmalnik > > Cc: Kevin Grittner; pgsql-admin@postgresql.org > > Subject: Re: [ADMIN] Autovacuum stopped running > > > > "Benjamin Krajmalnik" writes: > > > 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. > > > > We've seen one or two previous reports that suggested that the > autovac > > launcher might have stopped launching workers, but it hasn't been > > reproducible. Are you using any nonstandard parameters for > autovacuum? > > > > regards, tom lane