Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 41283634087 for ; Wed, 16 Jun 2010 17:54:09 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 76665-10 for ; Wed, 16 Jun 2010 20:54:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id D68A1633804 for ; Wed, 16 Jun 2010 17:54:01 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id 5B6AC34803A; Wed, 16 Jun 2010 13:54:00 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kchcvQS-S1P7; Wed, 16 Jun 2010 13:53:54 -0700 (PDT) Received: from perhan.alvh.no-ip.org (190-95-18-56.bk17-dsl.surnet.cl [190.95.18.56]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id 8D98B348037; Wed, 16 Jun 2010 13:53:54 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 0A6DE6E64B; Wed, 16 Jun 2010 16:53:52 -0400 (CLT) Content-Type: text/plain; charset=UTF-8 Cc: Scott Carey , Greg Smith , Tom Wilcox , Bob Lunney , "pgsql-performance@postgresql.org" Subject: Re: requested shared memory size overflows size_t From: Alvaro Herrera To: Tom Lane In-reply-to: <26740.1276574231@sss.pgh.pa.us> References: <584872.74177.qm@web39702.mail.mud.yahoo.com> <4C167A8D.1060002@gmail.com> <4C16E039.10803@2ndquadrant.com> <08A32E7F-5FFC-4341-A543-E0BFB6420B7E@richrelevance.com> <26740.1276574231@sss.pgh.pa.us> Date: Wed, 16 Jun 2010 16:53:52 -0400 Message-Id: <1276721410-sup-6820@alvh.no-ip.org> User-Agent: Sup/0.11 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.001 tagged_above=-10 required=5 tests=BAYES_20=-0.001 X-Spam-Level: X-Archive-Number: 201006/300 X-Sequence-Number: 39156 Excerpts from Tom Lane's message of lun jun 14 23:57:11 -0400 2010: > Scott Carey writes: > > Great points. There is one other option that is decent for the WAL: > > If splitting out a volume is not acceptable for the OS and WAL -- absolutely split those two out into their own partitions. It is most important to make sure that WAL and data are not on the same filesystem, especially if ext3 is involved. > > Uh, no, WAL really needs to be on its own *spindle*. The whole point > here is to have one disk head sitting on the WAL and not doing anything > else except writing to that file. However, there's another point here -- probably what Scott is on about: on Linux (at least ext3), an fsync of any file does not limit to flushing that file's blocks -- it flushes *ALL* blocks on *ALL* files in the filesystem. This is particularly problematic if you have pgsql_tmp in the same filesystem and do lots of disk-based sorts. So if you have it in the same spindle but on a different filesystem, at least you'll avoid that extra fsync work, even if you have to live with the extra seeking. -- Álvaro Herrera The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support