> You are looking for tablespaces :).
I don't doubt that he is.
... but wouldn't something as simple as RAID 1+0 give much of the same
benefit (being able to distribute the IO load to more disks), but without
the danger of incorrectly placing the table spaces?
---(end o
On Mon, Jan 29, 2007 at 11:50:35 +0900,
Paul Lambert <[EMAIL PROTECTED]> wrote:
>
> In order to balance disk load and ensure faster data access, my current
> SQL server setup has the data spread across 3 physical disk devices. One
> question I would like to know which I can't find in the docum
Paul Lambert wrote:
> Im in the process of finalising my conversion from M$ SQL server to
> Postgres - all of which I'm very happy about so far.
>
> The database I work with has 37 tables, 5 of which run into the order of
> tens of millions of records and approximately another 10 can run into
> mi
Paul Lambert <[EMAIL PROTECTED]> writes:
> I.e. can I create a data file on D drive which holds tables a, b and
> e, and a data file on E drive which holds tables c, d and f.
>
> If this is possible, could someone point me to some documentation so I
> can experiment a little.
Read the doc section
Im in the process of finalising my conversion from M$ SQL server to
Postgres - all of which I'm very happy about so far.
The database I work with has 37 tables, 5 of which run into the order of
tens of millions of records and approximately another 10 can run into
millions depending on the size
