[jasdeepkhalsa]

Uses @dbdiff/cli 3.0.0-rc.32 and @akal/pg-conformance 0.0.17.

• DBDiff rc.32 fixes array and extension type modifiers, mixed-case domains, in-place domain changes, columns added to partitioned tables, partitions in another schema than their parent, partitioned tables' own sequences, and PostgreSQL 18 virtual generated columns.
• The real-world job's known gaps for those are removed; the job fails if any of them still fails, and on any listed gap that starts passing.
• pg-conformance 0.0.17 adds six corpus cases for the same shapes, which the scenario suites now run.

With those failures gone, the job reaches shapes it never got to before. Each already failed under rc.31, and is now listed with its reason:

• PostgreSQL 18 NOT NULL constraint names on partitions created with PARTITION OF (Pagila), and on a renamed table across PostgreSQL 17 and 18, which --prove correctly refuses (AdventureWorks pg17>pg18).
• The built-in renderer, which partitioned tables always use, writing columns that own a sequence with its own options or name as bigserial; partitions' indexes taking generated names (GitLab).
• Supabase keeping uuid-ossp in its extensions schema (AdventureWorks pg17>sb15).

Already listed: clone does not copy privileges, and a Supabase target synced from plain PostgreSQL keeps reporting Supabase's own extensions and realtime publication.

🤖 Generated with Claude Code