Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XCTI4-0003wP-5B for pgsql-performance@arkaria.postgresql.org; Wed, 30 Jul 2014 12:47:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XCTI3-0004O7-GA for pgsql-performance@arkaria.postgresql.org; Wed, 30 Jul 2014 12:47:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XCTI2-0004Nu-9l for pgsql-performance@postgresql.org; Wed, 30 Jul 2014 12:47:30 +0000 Received: from smtp-out1.gransy.com ([77.78.126.51]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XCTHz-0003SZ-0r for pgsql-performance@postgresql.org; Wed, 30 Jul 2014 12:47:29 +0000 Received: from smtp-out.gransy.com (localhost [127.0.0.1]) by smtp-out1.gransy.com (Postfix) with ESMTP id 9217A36004E for ; Wed, 30 Jul 2014 14:47:25 +0200 (CEST) Received: from smtp.gransy.com (smtp.simplia.cz [77.78.126.20]) by smtp-out1.gransy.com (Postfix) with ESMTP id 4C7DB360005; Wed, 30 Jul 2014 14:47:25 +0200 (CEST) Received: from sq.gransy.com (elizabeth.gransy.com [89.187.132.199]) (Authenticated sender: tv@fuzzy.cz) by smtp.gransy.com (Postfix) with ESMTPA id 731AA19A0582; Wed, 30 Jul 2014 14:47:21 +0200 (CEST) Received: from 212.47.19.46 (SquirrelMail authenticated user tv@fuzzy.cz) by sq.gransy.com with HTTP; Wed, 30 Jul 2014 14:47:23 +0200 Message-ID: <11b808bce5fce4547fdcac5e94acb440.squirrel@sq.gransy.com> In-Reply-To: <26683.1406723992@sss.pgh.pa.us> References: <53ACB190.2030206@catalyst.net.nz> <53ACD6C4.9050605@catalyst.net.nz> <20140627091951.GA16680@awork2.anarazel.de> <53B283F3.7020005@catalyst.net.nz> <20140701101307.GO21422@awork2.anarazel.de> <53BF326F.2070903@catalyst.net.nz> <20140711082207.GI17261@awork2.anarazel.de> <53C711B6.5040802@catalyst.net.nz> <53D84E16.90609@catalyst.net.nz> <3e6b532b0115ffff08e8d0debd76695b.squirrel@sq.gransy.com> <26683.1406723992@sss.pgh.pa.us> Date: Wed, 30 Jul 2014 14:47:23 +0200 Subject: Re: 60 core performance with 9.3 From: "Tomas Vondra" To: "Tom Lane" Cc: "Tomas Vondra" , "Mark Kirkwood" , "Andres Freund" , pgsql-performance@postgresql.org User-Agent: SquirrelMail/1.4.22 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 30 Červenec 2014, 14:39, Tom Lane wrote: > "Tomas Vondra" writes: >> On 30 ??ervenec 2014, 3:44, Mark Kirkwood wrote: >>> While these numbers look great in the middle range (12-96 clients), >>> then >>> benefit looks to be tailing off as client numbers increase. Also >>> running >>> with no stats (and hence no auto vacuum or analyze) is way too scary! > >> By disabling statistics collector you loose runtime counters - number of >> sequential/index scans on a table, tuples read from a relation aetc. But >> it does not influence VACUUM or planning at all. > > It does break autovacuum. Of course, you're right. It throws away info about how much data was modified and when the table was last (auto)vacuumed. This is a clear proof that I really need to drink at least one cup of coffee in the morning before doing anything in the morning. Tomas -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance