Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E4D662E3A86 for ; Sat, 12 Jan 2008 05:40:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 42060-08 for ; Sat, 12 Jan 2008 05:40:40 -0400 (AST) Received: from easy2.in-chemnitz.de (easy2.in-chemnitz.de [88.198.17.232]) by postgresql.org (Postfix) with ESMTP id E59882E32A7 for ; Sat, 12 Jan 2008 05:40:44 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by easy2.in-chemnitz.de (Postfix) with ESMTP id CA176227C2E for ; Sat, 12 Jan 2008 10:40:42 +0100 (CET) Received: from easy2.in-chemnitz.de ([127.0.0.1]) by localhost (easy.in-chemnitz.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WoRuUvawTE1i for ; Sat, 12 Jan 2008 10:40:42 +0100 (CET) Received: by easy2.in-chemnitz.de (Postfix, from userid 1013) id B9319227C3B; Sat, 12 Jan 2008 10:40:42 +0100 (CET) Date: Sat, 12 Jan 2008 10:40:42 +0100 From: Tino Schwarze To: pgsql-admin@postgresql.org Subject: Re: Fwd: physical memory Message-ID: <20080112094042.GA19328@easy2.in-chemnitz.de> References: <47865B81.9020104@gmail.com> <8fb205ea0801101034n70ce6abby6aebc73202742fa1@mail.gmail.com> <14770360.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <14770360.post@talk.nabble.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/128 X-Sequence-Number: 27902 On Sat, Jan 12, 2008 at 12:39:52AM -0800, Antonio5556 wrote: > My fear is that the tablespace is related to a specific directory of the OS; > and, in my best understanding on OS, the amount of memory of a directory is > bounded by the amount of memory of the related HD. Hence, when the amount of > memory related to such directory will run out of space it will not scale to > other HD. :rules: That's what Logical Volume Management (LVM) is for - it allows you to have a filesystem which spans multiple HDs (or RAIDs). So this is not an issue of PostgreSQL but of the operating system. Tino. -- www.craniosacralzentrum.de www.spiritualdesign-chemnitz.de Tino Schwarze * Parkstraße 17h * 09120 Chemnitz