fix: normalize whitespace after INTO clause insertion

When the parser strips 'INTO <target>' from a SELECT statement, it leaves
behind the original whitespace. This caused weird formatting like:
  SELECT x INTO y                                         FROM z

Now we normalize the whitespace:
- If original had newlines, use newline + 4-space indent
- If original was just spaces/tabs, collapse to single space

This fixes the pretty-printing issue with long INTO target lists.

Author: pyramation

packages/plpgsql-deparser/__tests__/__snapshots__/deparser-fixes.test.ts.snap

@@ -88,7 +88,7 @@ BEGIN
   INSERT INTO tokens (id, user_id, access_token_hash)
     VALUES (v_token_id, p_user_id, digest(v_plaintext_token, 'sha256'));
   SELECT tkn.id, tkn.user_id, v_plaintext_token, tkn.access_token_expires_at, tkn.is_verified, tkn.totp_enabled INTO id, user_id, access_token, access_token_expires_at, is_verified, totp_enabled
-                                                                                         FROM tokens AS tkn
+      FROM tokens AS tkn
     WHERE tkn.id = v_token_id;
   RETURN;
 END"

packages/plpgsql-deparser/__tests__/__snapshots__/hydrate-demo.test.ts.snap

@@ -98,7 +98,7 @@ BEGIN
         t.orders_scanned,
         t.gross_total,
         t.avg_total INTO v_orders_scanned, v_gross, v_avg
-      FROM totals AS t;
+          FROM totals AS t;
       IF p_apply_discount THEN
             v_rebate := round(v_gross * GREATEST(LEAST(v_discount_rate + v_jitter, 0.50), 0), p_round_to);
       ELSE
@@ -109,7 +109,7 @@ BEGIN
       SELECT
         oi.sku,
         CAST(sum(oi.quantity) AS bigint) AS qty INTO v_top_sku, v_top_sku_qty
-      FROM app_public.order_item AS oi
+          FROM app_public.order_item AS oi
       JOIN app_public.app_order AS o ON o.id = oi.order_id
       WHERE
         o.org_id = p_org_id

packages/plpgsql-deparser/__tests__/__snapshots__/schema-rename-mapped.test.ts.snap

@@ -194,7 +194,7 @@ exports[`schema rename mapped should transform schema names and snapshot schema
   total_count int;
 BEGIN
   SELECT count(*) INTO total_count
-  FROM myapp_v2.users AS u
+      FROM myapp_v2.users AS u
   JOIN myapp_v2.orders AS o ON o.user_id = u.id
   WHERE
     u.id = p_user_id;
@@ -270,7 +270,7 @@ CREATE FUNCTION myapp_v2.calculate_order_total(
   discount numeric;
 BEGIN
   SELECT sum(quantity * price) INTO subtotal
-  FROM myapp_v2.order_items
+      FROM myapp_v2.order_items
   WHERE
     order_id = p_order_id;
   tax_amount := myapp_v2.get_tax_rate() * subtotal;

packages/plpgsql-deparser/src/plpgsql-deparser.ts

@@ -1485,8 +1485,23 @@ export class PLpgSQLDeparser {
         // large gaps like "SELECT x INTO y                    FROM z"
         const before = sql.slice(0, insertPos);
         let after = sql.slice(insertPos);
-        // Collapse leading whitespace (but preserve a single space before the next keyword)
-        after = after.replace(/^[ \t]+/, ' ');
+        // Normalize whitespace after INTO insertion
+        // The parser strips "INTO <target>" but leaves whitespace behind, which can cause
+        // weird formatting like "SELECT x INTO y                    FROM z"
+        // We collapse all whitespace to either a single space or a newline with standard indent
+        const leadingWsMatch = after.match(/^(\s+)/);
+        if (leadingWsMatch) {
+          const ws = leadingWsMatch[1];
+          const hasNewline = /\n/.test(ws);
+          if (hasNewline) {
+            // If original had newlines, use a newline with standard 4-space indent
+            // This normalizes any weird indentation left by the parser
+            after = after.replace(/^\s+/, '\n    ');
+          } else {
+            // If original was just spaces/tabs, collapse to single space
+            after = after.replace(/^[ \t]+/, ' ');
+          }
+        }
         sql = before + intoClause + after;
       } else {
         // -1 means INTO already exists at depth 0, don't add another one