Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id C419A9FA4A7 for ; Fri, 29 Sep 2006 10:31:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 42651-02 for ; Fri, 29 Sep 2006 10:31:33 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by postgresql.org (Postfix) with ESMTP id 67B239FA2A9 for ; Fri, 29 Sep 2006 10:31:33 -0300 (ADT) Received: from pool-72-88-194-29.nwrknj.fios.verizon.net ([72.88.194.29] helo=[192.168.4.67]) by outbound.mailhop.org with esmtpa (Exim 4.51) id 1GTISh-0007fo-T3; Fri, 29 Sep 2006 09:31:31 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 72.88.194.29 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: tocr Message-ID: <451D2044.30903@zeut.net> Date: Fri, 29 Sep 2006 09:31:48 -0400 From: "Matthew T. O'Connor" User-Agent: Thunderbird 2.0a1 (Windows/20060724) MIME-Version: 1.0 To: Sriram Dandapani CC: pgsql-admin@postgresql.org Subject: Re: autovacuum ignore tables References: <6992E470F12A444BB787B5C937B9D4DF060E5B49@ca-mail1.cis.local> In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF060E5B49@ca-mail1.cis.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.049 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS X-Spam-Level: X-Archive-Number: 200609/362 X-Sequence-Number: 23276 Sriram Dandapani wrote: > The only issue I have with autovacuum is the fact that I have to briefly > stop/restart postgres every couple of days, which kills autovacuum and > it has no memory of previous work done. I work with several databases > with partitioned tables having high daily volume. Dropping partitioned > tables locks out jdbc inserts and the drop command itself goes into a > WAIT state. Hence, I have to stop postgres,update pg_hba.conf to prevent > access,restart postgres,drop tables and update pg_hba to allow > access(Crazy, but I have no choice because Postgres deadlocks on drop > child tables while inserts happen on the parent) Sounds like a fairly serious problem, but I'll let someone else talk to that. As for the autovac issue, as of 8.1 and autovac being integrated into core, this isn't true. It does remember where it was, at least as long as you don't have the GUC var reset_stats_on_restart (something like that) set. Matt