Re: clarification of postgres limitations

From: mbc(at)soliton(dot)com
To: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: clarification of postgres limitations
Date: 2004-03-04 18:10:43
Message-ID: 20040304181043.GB25598@oyster.tor.soliton.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)marlowe(at)ihs(dot)com>
>Subject: Re: [GENERAL] clarification of postgres limitations
>To: mbc(at)soliton(dot)com
>cc: pgsql-general(at)postgresql(dot)org
>Date: Thu, 4 Mar 2004 10:49:49 -0700 (MST)
>Message-ID: <Pine(dot)LNX(dot)4(dot)33(dot)0403041048240(dot)11855-100000(at)css120(dot)ihs(dot)com>
>
>On Thu, 4 Mar 2004 mbc(at)soliton(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-03-04 21:07:21 Re: Setting up Postgresql on Linux
Previous Message scott.marlowe 2004-03-04 17:49:49 Re: clarification of postgres limitations