Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id B56262E389A for ; Sat, 12 Jan 2008 04:39:59 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 47957-02 for ; Sat, 12 Jan 2008 04:39:52 -0400 (AST) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by postgresql.org (Postfix) with ESMTP id 85A9F2E38A6 for ; Sat, 12 Jan 2008 04:39:54 -0400 (AST) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JDbuD-0006dH-08 for pgsql-admin@postgresql.org; Sat, 12 Jan 2008 00:39:53 -0800 Message-ID: <14770360.post@talk.nabble.com> Date: Sat, 12 Jan 2008 00:39:52 -0800 (PST) From: Antonio5556 To: pgsql-admin@postgresql.org Subject: Re: Fwd: physical memory In-Reply-To: <8fb205ea0801101034n70ce6abby6aebc73202742fa1@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: antonio.corardi@gmail.com References: <47865B81.9020104@gmail.com> <8fb205ea0801101034n70ce6abby6aebc73202742fa1@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.03 tagged_above=0 required=5 tests=BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, WHOIS_MYPRIVREG=1.499 X-Spam-Level: X-Archive-Number: 200801/127 X-Sequence-Number: 27901 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: Richmond Dyes-2 wrote: > > ---------- Forwarded message ---------- > From: Rich > Date: Jan 10, 2008 1:32 PM > Subject: Re: [ADMIN] physical memory > To: Antonio Corardi > > ... > Example if you put your tabelspace on a system where the filesystem > spans multiple drives, it will grow till you run out of space. This I > would say is based on your filesystem design. > > > ... > > -- View this message in context: http://www.nabble.com/physical-memory-tp14739957p14770360.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com.