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 04EEAEAE486 for ; Fri, 22 Oct 2004 22:13:12 +0100 (BST) 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 67643-07 for ; Fri, 22 Oct 2004 21:13:11 +0000 (GMT) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id 26798EAE4AC for ; Fri, 22 Oct 2004 22:13:02 +0100 (BST) Received: from ool-4350c7ad.dyn.optonline.net ([67.80.199.173] helo=[192.168.0.66]) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.42) id 1CL6iu-0001Bf-BH; Fri, 22 Oct 2004 17:13:20 -0400 Message-ID: <417977EE.8050207@zeut.net> Date: Fri, 22 Oct 2004 17:13:18 -0400 From: "Matthew T. O'Connor" Organization: Terrie O'Connor Realtors User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Sullivan Cc: PgSQL - Performance Subject: Re: Performance Anomalies in 7.4.5 References: <25228.1098395599@sss.pgh.pa.us> <20041022194058.GC22395@phlogiston.dyndns.org> In-Reply-To: <20041022194058.GC22395@phlogiston.dyndns.org> 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.80.199.173 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.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/382 X-Sequence-Number: 8858 Andrew Sullivan wrote: >>Probably the most severe objection to doing things this way is that the >>selected plan could change unexpectedly as a result of the physical >>table size changing. Right now the DBA can keep tight rein on actions >>that might affect plan selection (ie, VACUUM and ANALYZE), but that >>would go by the board with this. OTOH, we seem to be moving towards >>autovacuum, which also takes away any guarantees in this department. >> >> > >But aren't we requiring that we can disable autovacuum on some >tables? > Yes that is the long term goal, but the autovac in 8.0 is still all or nothing.