Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 7981B55C5A4 for ; Mon, 16 Jul 2012 13:57:54 -0300 (ADT) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SqocL-0004H6-Qb for pgsql-hackers@postgresql.org; Mon, 16 Jul 2012 16:57:54 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q6GGvdIM013012; Mon, 16 Jul 2012 12:57:39 -0400 (EDT) From: Tom Lane To: Robert Haas cc: Jeff Janes , pgsql-hackers , Daniel Farina , Craig Ringer , =?ISO-8859-1?Q?Harold_A=2E_Gim=E9nez?= Subject: Re: [PERFORM] DELETE vs TRUNCATE explanation In-reply-to: References: <4FFCCAC4.4030503@ringerc.id.au> <23853.1342015548@sss.pgh.pa.us> <32078D4B40DD40ECB739D0ECD7D95996@gmail.com> <19949.1342376967@sss.pgh.pa.us> <9603.1342454919@sss.pgh.pa.us> <11952.1342456591@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Mon, 16 Jul 2012 12:53:02 -0400" Date: Mon, 16 Jul 2012 12:57:39 -0400 Message-ID: <13011.1342457859@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201207/718 X-Sequence-Number: 211401 Robert Haas writes: > In my view, the elephant in the room here is that it's dramatically > inefficient for every backend to send an fsync request on every block > write. Yeah. This was better before the decision was taken to separate bgwriter from checkpointer; before that, only local communication was involved for the bulk of write operations (or at least so we hope). I remain less than convinced that that split was really a great idea. regards, tom lane