|
From: Nicholas G. <ngo...@ba...> - 2008-11-05 02:23:48
|
On Nov 4, 2008, at 5:06 PM, John V. Sichi wrote: > work, and also decide on the best way to support the "movable" use > case > you mention (for that, a correspondence between logical schema and > physical tablespace is desirable, whereas for general purposes it's > nice > to keep physical and logical containment independent). <random-thoughts> What about keeping an export of the catalog to go along with every label? The label seems like a natural way to do backups/checkpoints in addition to read/load consistency. If there was a way to, as part of the label creation logic, create a snapshot of the catalog at that point in time it could make hot backups/moving/etc easier. As a warehouse user, knowing that absolutely, 100% hot backups are not really needed, the label feels like it could be part of a great asynchronous backup/movement/ replication/etc framework. Create the label and a scheduled process simply periodically creates backups "up to" the latest label (but not current which is more complicated. </random-thoughts> Nick |