Josh Berkus wrote:
> The whole point of tablespaces is to > allow placing individual tables and indexes > on seperate volumes.
That was one reason. I seem to recall several more:
* Putting data on cost appropriate media Mentioned previously in this thread
* Balancing I/O across spindles Also mentioned previously, many times
* Inode stability
The free space bitmap never changes during production. The inode table never changes during production (save for last modified and last accessed timestamps). This makes the filesystem VERY likely to be functional in case of a crash. Jounaled file systems have reduced the need for this.
* Device independence
Since a tablespace needs only some "file names" and the ability to lseek() to any point in a file, a tablespace file can be a file on the UFS (or its variantes), a disk partition, or even a tape drive device.
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
