Format PL/pgSQL ALIAS, RETURN NEXT, and FOR-over-query

[gmr]

Summary

Companion to tree-sitter-postgres #42. Once the grammar parses the new PL/pgSQL constructs, the formatter still rendered three of them incorrectly:

• ALIAS declarations dropped their target — username ALIAS FOR $1; became username;. Now emits the full name ALIAS FOR target form.
• RETURN NEXT / RETURN QUERY dropped the NEXT/QUERY keyword (RETURN NEXT; → RETURN;). Now emitted, including optional EXECUTE and a trailing expression.
• FOR-over-query dropped the query text after IN because the formatter looked for a non-existent for_control node. Now takes the matched for_* variant (for_query/for_integer_range/for_cursor/for_dynamic) up to its nested LOOP keyword.

Adds regression tests covering all three plus multi-word types and DEFAULT.

⚠️ Blocked on tree-sitter-postgres 1.2.3

The new tests parse constructs that only the grammar in gmr/tree-sitter-postgres#42 understands. CI will be red until that PR is merged, released as 1.2.3, and the dependency here is bumped (tree-sitter-postgres = "1.2.3"). That dep bump is the final step before merge.

Verified locally against the #42 grammar (via a path patch): full suite green, all 23 previously-failing production functions format faithfully.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@gmr, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 28 minutes and 27 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 18939966-9f93-4925-bfad-7a0f3322cef4

📥 Commits

Reviewing files that changed from the base of the PR and between 1d1ca7d and 03f54a5.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• Cargo.toml
• src/formatter/plpgsql.rs
• tests/plpgsql_test.rs

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}