Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 0546F1AB3538 for ; Wed, 18 Jul 2012 04:30:57 -0300 (ADT) Received: from mail-wi0-f172.google.com ([209.85.212.172]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SrOim-0008IQ-GJ for pgsql-hackers@postgresql.org; Wed, 18 Jul 2012 07:30:57 +0000 Received: by wibhm11 with SMTP id hm11so4469031wib.1 for ; Wed, 18 Jul 2012 00:30:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=Y6yUAZNm2IVPSBdTDtm6vi0NdKZI98EMhUIfrpn/G4A=; b=fsQZniDamwtxIHyL1FdzHCHhBjHsBP1wJN/I57VuvOHOzoCCaaZUQZ6cELKqzZiTK9 onxLns+LWw1cjH77CxXmupJHRoixUyHMmJuGCShOFGn8kL2sByTZ0ZNGc5RLEu4Bds7P 6F0a/CeKzYpORECIrVDsy8NPR/w5qrI0pHlQDNEA5YXIawfRENvwXr+iGhsEwE4Pei3x FYihCT7snxWA2tBN4t7DWVQFFZEg7aVJSQ4YM5qVl93aqsCc75g9lDXXo/1i+8Ui4wkY lf0LFtuFfy/tKpTP/NwLCJ2KXJMaUHc+snq/3zZoc5ipnOYtYxYmmExaIWrv2aYYR+aH tkMQ== Received: by 10.217.7.6 with SMTP id z6mr1181198wes.5.1342596642882; Wed, 18 Jul 2012 00:30:42 -0700 (PDT) Received: from [192.168.62.52] (88-196-201-198-dsl.rkv.estpak.ee. [88.196.201.198]) by mx.google.com with ESMTPS id w7sm31236552wiz.0.2012.07.18.00.30.41 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 Jul 2012 00:30:42 -0700 (PDT) Message-ID: <50066620.7090501@enterprisedb.com> Date: Wed, 18 Jul 2012 10:30:40 +0300 From: Heikki Linnakangas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120510 Icedove/10.0.4 MIME-Version: 1.0 To: Peter Geoghegan CC: Tom Lane , Robert Haas , Jeff Janes , pgsql-hackers , Daniel Farina , Craig Ringer , =?ISO-8859-1?Q?=22Harold_A=2E_?= =?ISO-8859-1?Q?Gim=E9nez=22?= Subject: Re: Checkpointer split has broken things dramatically (was Re: DELETE vs TRUNCATE explanation) References: <4FFCCAC4.4030503@ringerc.id.au> <32078D4B40DD40ECB739D0ECD7D95996@gmail.com> <19949.1342376967@sss.pgh.pa.us> <9603.1342454919@sss.pgh.pa.us> <11952.1342456591@sss.pgh.pa.us> <13011.1342457859@sss.pgh.pa.us> <15955.1342466333@sss.pgh.pa.us> <9247.1342565810@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQkFKLwquz0es6eMzXPcFcmvW5sB1Z/dKT7W01eA+J5OTRD/VTq7pLx9002+or+Ibjh/Xdhe X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201207/785 X-Sequence-Number: 211468 On 18.07.2012 02:48, Peter Geoghegan wrote: > On 17 July 2012 23:56, Tom Lane wrote: >> This implies that nobody has done pull-the-plug testing on either HEAD >> or 9.2 since the checkpointer split went in (2011-11-01), because even >> a modicum of such testing would surely have shown that we're failing to >> fsync a significant fraction of our write traffic. >> >> Furthermore, I would say that any performance testing done since then, >> if it wasn't looking at purely read-only scenarios, isn't worth the >> electrons it's written on. In particular, any performance gain that >> anybody might have attributed to the checkpointer splitup is very >> probably hogwash. >> >> This is not giving me a warm feeling about our testing practices. > > The checkpointer slit-up was not justified as a performance > optimisation so much as a re-factoring effort that might have some > concomitant performance benefits. Agreed, but it means that we need to re-run the tests that were done to make sure the extra fsync-request traffic is not causing a performance regression, http://archives.postgresql.org/pgsql-hackers/2011-10/msg01321.php. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com