Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id ADD4A2E0275 for ; Thu, 10 Jan 2008 14:34:09 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 46921-05 for ; Thu, 10 Jan 2008 14:34:06 -0400 (AST) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.228]) by postgresql.org (Postfix) with ESMTP id DF93C2E01D5 for ; Thu, 10 Jan 2008 14:34:06 -0400 (AST) Received: by nz-out-0506.google.com with SMTP id l8so429774nzf.28 for ; Thu, 10 Jan 2008 10:34:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=gz60YOSeftJJNYCW2uX1MGKPe6a8lVin8SfGhG+tWb8=; b=WM1DEWy8yLaiZi1nfXJIF+/U9+UIXIpzvN49ag1ZTAdrMAHD0Qk/Q4nLmEGm6787MwNnLAHch8M62sEpTXRb3z+1/Mhd5e1VlxN70WNNXHlfSsh5KSR+/O1sFbxZnmZfIBFo17c/E2YBSyCKsObq5wWDwiNZim+RMGd4J8g0qsk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=xlGcEgVl94gRY4dwm9umDe/Emh6MC9op9z7lIbA1k8zlMgA3UId+pLkhKwiOxtvLtFe9yGnxOQACNutNeAHIWr9o+0rlY6KFqLWZSHqUR146FpCTko5y1032Z5DxddZj7Hj1suQbqIABj0M8WBJUItN6dxPdCLn0Mtd6eRUhucQ= Received: by 10.114.75.1 with SMTP id x1mr2586373waa.137.1199990045485; Thu, 10 Jan 2008 10:34:05 -0800 (PST) Received: by 10.115.76.19 with HTTP; Thu, 10 Jan 2008 10:34:05 -0800 (PST) Message-ID: <8fb205ea0801101034n70ce6abby6aebc73202742fa1@mail.gmail.com> Date: Thu, 10 Jan 2008 13:34:05 -0500 From: Rich To: pgsql-admin@postgresql.org Subject: Fwd: physical memory In-Reply-To: <8fb205ea0801101032i2b3f45e1o3721a6bbfc75c1d9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47865B81.9020104@gmail.com> <8fb205ea0801101032i2b3f45e1o3721a6bbfc75c1d9@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/109 X-Sequence-Number: 27883 ---------- Forwarded message ---------- From: Rich Date: Jan 10, 2008 1:32 PM Subject: Re: [ADMIN] physical memory To: Antonio Corardi There is probably no limit except the limitations of your hardware at this time. As far as it automatically incorporating other hard drives, that is probably more of a function of your operating system. 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. On Jan 10, 2008 12:53 PM, Antonio Corardi wrote: > Hi all, > I'm new here and my doubt is very basic. I'm wondering how to set > the max amount of space(physical, not RAM) to be used by postgreSQL. > Moreover, Is such amount limited to the hard disk in wich postgreSQL is > installed or it scales automatically to the others HD available? How > can I manage it. > Thanks in advance. > Antonio > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend >