Method on_copy_done

nodedb/src/control/server/pgwire/handler/copy_handler.rs:128–170

(&self, client: &mut C, _done: CopyDone)

    }

    async fn on_copy_done<C>(&self, client: &mut C, _done: CopyDone) -> PgWireResult<()>
    where
        C: ClientInfo + Sink<PgWireBackendMessage> + Unpin + Send + Sync,
        C::Error: Debug,
        PgWireError: From<<C as Sink<PgWireBackendMessage>>::Error>,
    {
        let id = conn_id(&client.socket_addr());
        let pending = self.restore_state.take(id).ok_or_else(|| {
            sqlstate(
                ss::FEATURE_NOT_SUPPORTED,
                "no restore pending on this connection",
            )
        })?;
        let stats = backup::restore_tenant(
            &self.state,
            pending.tenant_id,
            &pending.bytes,
            pending.dry_run,
        )
        .await
        .map_err(internal)?;
        // pgwire does not auto-send CommandComplete after `on_copy_done`
        // returns Ok — the trait contract leaves message construction to
        // the handler. Send a `RESTORE TENANT N <op-count>` tag so the
        // client's COPY IN sink can complete.
        let rows =
            stats.documents + stats.kv_tables + stats.vectors + stats.timeseries + stats.edges;
        let tag = Tag::new("RESTORE TENANT").with_rows(rows);
        client
            .send(PgWireBackendMessage::CommandComplete(tag.into()))
            .await
            .map_err(|e| {
                sqlstate(
                    ss::INTERNAL_ERROR,
                    &format!("CommandComplete send failed: {e:?}"),
                )
            })?;
        // Leave the COPY-in-progress state so the next Sync from the
        // client gets dispatched normally. pgwire's `process_message`
        // only routes Sync via the `AwaitingSync` arm.
        client.set_state(PgWireConnectionState::AwaitingSync);
        Ok(())
    }
}

fn conn_id(addr: &SocketAddr) -> u64 {