Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id E62E79FB2AB for ; Thu, 18 Jan 2007 17:53:26 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 49000-04-2 for ; Thu, 18 Jan 2007 17:53:14 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by postgresql.org (Postfix) with ESMTP id C10039FB1D2 for ; Thu, 18 Jan 2007 17:53:22 -0400 (AST) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 01C4D8420E; Thu, 18 Jan 2007 16:53:21 -0500 (EST) Received: from web2.messagingengine.com ([10.202.2.211]) by out1.internal (MEProxy); Thu, 18 Jan 2007 16:53:22 -0500 Received: by web2.messagingengine.com (Postfix, from userid 99) id BF1BA8AC7; Thu, 18 Jan 2007 16:53:21 -0500 (EST) Message-Id: <1169157201.18501.1169996967@webmail.messagingengine.com> X-Sasl-Enc: TiGOhxOLtISwLLKT+FHaOGbLjhD/6A7IYvlure0uLUlW 1169157201 From: "Jeremy Haile" To: "Tom Lane" Cc: "Matthew T. O'Connor" , pgsql-performance@postgresql.org Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface References: <1169145474.20103.1169962769@webmail.messagingengine.com> <45AFC86B.9010704@zeut.net> <1169151707.6247.1169971737@webmail.messagingengine.com> <6362.1169155817@sss.pgh.pa.us> Subject: Re: Autoanalyze settings with zero scale factor In-Reply-To: <6362.1169155817@sss.pgh.pa.us> Date: Thu, 18 Jan 2007 16:53:21 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/325 X-Sequence-Number: 22926 Well - it hadn't run on any table in over 24 hours (according to pg_stat_user_tables). My tables are constantly being inserted into and deleted from, and the autovacuum settings are pretty aggressive. I also had not seen the autovac process running in the past 24 hours. (although I wasn't watching it *all* the time) So - as far as I could tell it wasn't running. On Thu, 18 Jan 2007 16:30:17 -0500, "Tom Lane" said: > "Jeremy Haile" writes: > > No tables have been vacuumed or analyzed today. I had thought that this > > problem was due to my pg_autovacuum changes, but perhaps not. I > > restarted PostgreSQL (in production - yikes) About a minute after being > > restarted, the autovac process fired up. > > > What could get PG in a state where autovac isn't running? > > Um, are you sure it wasn't? The autovac process is not an always-there > thing, it quits after each pass and then the postmaster starts a new one > awhile later. > > regards, tom lane