fix: Use fresh admin connection after DROP DATABASE

When dropping and recreating a database, the original target_client
was connected to the database being dropped. After DROP DATABASE,
PostgreSQL terminates that connection, causing subsequent CREATE
DATABASE to fail with "connection closed".

Now connects to 'postgres' admin database for CREATE DATABASE,
mirroring the approach already used in drop_database_if_exists().

Author: taariq

src/commands/init.rs

@@ -480,12 +480,17 @@ pub async fn init(
                                 if should_drop {
                                     drop_database_if_exists(target_url, &db_info.name).await?;
 
-                                    // Recreate the database
+                                    // Recreate the database using a fresh connection to 'postgres'
+                                    // (target_client was connected to the dropped database and is now dead)
+                                    let admin_url =
+                                        replace_database_in_url(target_url, "postgres")?;
+                                    let admin_client =
+                                        postgres::connect_with_retry(&admin_url).await?;
                                     let create_query = format!(
                                         "CREATE DATABASE {}",
                                         crate::utils::quote_ident(&db_info.name)
                                     );
-                                    target_client
+                                    admin_client
                                         .execute(&create_query, &[])
                                         .await
                                         .with_context(|| {