store: Take ownership of self in CopyConnection.copy_data

This ensures that `copy_data` can't be called more than once on any
instance; when copying encounters an error, it might leave the
CopyConnection in an inconsistent state and should therefore not be reused

Author: lutter

store/postgres/src/copy.rs

@@ -1142,7 +1142,7 @@ impl Connection {
     /// lower(v1.block_range) => v2.vid > v1.vid` and we can therefore stop
     /// the copying of each table as soon as we hit `max_vid = max { v.vid |
     /// lower(v.block_range) <= target_block.number }`.
-    pub async fn copy_data(&mut self, index_list: IndexList) -> Result<Status, StoreError> {
+    pub async fn copy_data(mut self, index_list: IndexList) -> Result<Status, StoreError> {
         // We require sole access to the destination site, and that we get a
         // consistent view of what has been copied so far. In general, that
         // is always true. It can happen though that this function runs when

store/postgres/src/deployment_store.rs

@@ -1519,7 +1519,7 @@ impl DeploymentStore {
             // as adding new tables in `self`; we only need to check that tables
             // that actually need to be copied from the source are compatible
             // with the corresponding tables in `self`
-            let mut copy_conn = crate::copy::Connection::new(
+            let copy_conn = crate::copy::Connection::new(
                 logger,
                 self.pool.clone(),
                 src.clone(),