Marc Dirix wrote:
Op 9-okt-2006, om 23:39 heeft Ming-Wei Shih het volgende geschreven:
Mysql with innodb does support raw device but does not support table
space AFAIK
but postgresql does support table space.
They both use tablespace with a different meaning. In postgresql you
can define a tablespace
to a given directory, where it will store *all* data in that tablespace.
Just to explain it a little more fully, in PostgreSQL, that means that
you can assign different partitions/discs to different tables, ergo your
total database can be spread over multiple discs on a per-table basis.
Also, you can do things like store your WAL (write-ahead log) for
transaction recovery to another partition/disc.
I should mention that PostgreSQL 8.x also supports "horizontal
partitioning" where one table can be spread across multiple discs.
(http://www.postgresql.org/docs/8.1/interactive/ddl-partitioning.html).
The functionality is even more flexibly supported in 8.2, which is due
out any week
(http://developer.postgresql.org/pgdocs/postgres/release-8-2.html).
Regards,
Rick Morris
While in MySQL tablespace is a way to concatonate more harddisk room
to your database
i.e. spread over 2 discs if the first is full.
I don't have experience with Oracle and dbmail, I don't even now if
it is supported. I
would say go with open source and the money you save can buy you more
disks
(remember more spindle more joy) and maybe you want to donate to this
project
to get better support.
No oracle support as off version 2.0, however as paul said before, he
is willing to implement this in exchange for payment. So if you want
this you'd better contact him directly.
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail