X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 3E31356478 for ; Mon, 28 Feb 2005 14:31:08 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 09455-05 for ; Mon, 28 Feb 2005 14:31:06 +0000 (GMT) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id B20B25646D for ; Mon, 28 Feb 2005 14:31:06 +0000 (GMT) Received: from ool-43529386.dyn.optonline.net ([67.82.147.134] helo=[192.168.1.100]) by outbound.mailhop.org with esmtpa (Exim 4.44) id 1D5lvF-000AkJ-BT; Mon, 28 Feb 2005 09:30:57 -0500 Message-ID: <42232B22.4030302@zeut.net> Date: Mon, 28 Feb 2005 09:30:58 -0500 From: "Matthew T. O'Connor" User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gaetano Mendola Cc: Markus Schaber , Gaetano Mendola , pgsql-performance@postgresql.org Subject: Re: is pg_autovacuum so effective ? References: <12400.1109107683@sss.pgh.pa.us> <421BD64E.30803@bigfoot.com> <60psyr265t.fsf@dba2.int.libertyrms.com> <421CD6F0.8010406@zeut.net> <421DB36B.70004@bigfoot.com> <421DC4D5.1070909@logi-track.com> <421E556E.6010202@mbigroup.it> In-Reply-To: <421E556E.6010202@mbigroup.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop Outbound by DynDNS.org X-Originating-IP: 67.82.147.134 X-Report-Abuse-To: abuse@dyndns.org (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: zeut X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200502/369 X-Sequence-Number: 10698 Gaetano Mendola wrote: >Yes, I'm aware about it indeed I need the analyze because usualy I do on that >table select regarding last 24 ours so need to analyze it in order to >collect the statistics for this period. >Beside that I tried to partition that table, I used both tecnique on >my knowledge > >1) A view with UNION ALL on all tables collecting these logs >2) Using inheritance > >and both cases are working in theory but in practice are not ( the index scan >is lost as soon you use this view/table inside others views or joining them) > >I heard that next version of pg_autovacuum can be instructed "per table"; >is it true ? > The version of pg_autovacuum that I submitted for 8.0 could be instructed "per table" but it didn't make the cut. Aside from moved out of contrib and integrated into the backend, per table autovacuum settings is probably the next highest priority.