> The whole point here is: it is assumed that backup/restore of tablespaces can
> hapen quite quickly and as simple as to copy tablespace files from one
> location to another(even while database is on - WAL can be used to handle
> this) - this is compared to dump.
This is not going to happen. We intend to provide tablespaces in the
form of a simple management scheme for table files that are scattered
across multiple directories (typically on different filesystems).
That doesn't make it any safer to copy files behind the database's back.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
