Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id CFDAE65B309 for ; Tue, 16 Mar 2010 19:25:42 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 21447-05 for ; Tue, 16 Mar 2010 22:25:32 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 4F7F665B328 for ; Tue, 16 Mar 2010 19:25:32 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o2GMPQvn015896; Tue, 16 Mar 2010 18:25:26 -0400 (EDT) To: Alvaro Herrera cc: Greg Stark , Pierre C , Greg Smith , Dave Crooke , Paul McGarry , pgsql-performance@postgresql.org Subject: Re: shared_buffers advice In-reply-to: <20100316222058.GI3037@alvh.no-ip.org> References: <4B9F3302.4020900@2ndquadrant.com> <8285.1268749832@sss.pgh.pa.us> <407d949e1003160753o6e5faa48rabaa42f7548029b7@mail.gmail.com> <20100316213054.GG3037@alvh.no-ip.org> <15102.1268775566@sss.pgh.pa.us> <20100316214903.GH3037@alvh.no-ip.org> <15417.1268776714@sss.pgh.pa.us> <20100316222058.GI3037@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Tue, 16 Mar 2010 19:20:58 -0300" Date: Tue, 16 Mar 2010 18:25:26 -0400 Message-ID: <15895.1268778326@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/182 X-Sequence-Number: 38007 Alvaro Herrera writes: > Tom Lane escribió: >> That's not going to do anything towards reducing the actual I/O volume. >> Although I suppose it might be useful if it just cuts the number of >> seeks. > Oh, they had no problems with I/O volume. It was relation extension > lock that was heavily contended for them. Really? I guess that serialized all the I/O ... I'll bet if we got rid of that locking somehow, they *would* have a problem with I/O volume. regards, tom lane