Re: clarification of postgres limitations - Mailing list pgsql-general

From mbc@soliton.com
Subject Re: clarification of postgres limitations
Date
Msg-id 20040304181043.GB25598@oyster.tor.soliton.com
Whole thread Raw
In response to Re: clarification of postgres limitations  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-general
This is very good news.  Thank you very much.

On Thu, Mar 04, 2004 at 10:49:49AM -0700, scott.marlowe wrote:
>From: "scott.marlowe" <scott.marlowe@ihs.com>
>Subject: Re: [GENERAL] clarification of postgres limitations
>To: mbc@soliton.com
>cc: pgsql-general@postgresql.org
>Date: Thu, 4 Mar 2004 10:49:49 -0700 (MST)
>Message-ID: <Pine.LNX.4.33.0403041048240.11855-100000@css120.ihs.com>
>
>On Thu, 4 Mar 2004 mbc@soliton.com wrote:
>
>> Since it seems that the location of the server's data store is bound to a
>> single directory, a database cannot span across multiple file systems.
>> Further, does it imply that the maxiumum size of a database cannot exceed
>> the maximum size of the underlying file system?
>
>With 7.5 you'll be able to easily put database structures on more than one
>file system.
>
>As of 7.x series, the initlocation script allowed you to put individual
>databases within a cluster on different storage points:
>
>http://www.postgresql.org/docs/7.4/static/manage-ag-alternate-locs.html

--
"Nothing is either good or bad, but thinking makes it so."  -- Shakespeare
               Myron B. Cheung          Soliton Inc.

pgsql-general by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: clarification of postgres limitations
Next
From: Tom Lane
Date:
Subject: Re: Setting up Postgresql on Linux