Module constraint_metadata

Expand description

Normalize durable constraint names and identities through a caller-owned identity allocator.

Modules§

identity: Allocate constraint incarnations and preserve legacy NOT NULL OIDs during initial migration.

ConstraintNameScope: Explicit names share their relation’s event namespace; automatic names also avoid every constraint in the containing schema.

CatalogObjectAllocator: Declaration normalization requests identities from its caller. Execution reserves public addresses; isolated declarations and initial migration can derive candidates before validating the complete catalog.

choose_suffixed_constraint_name: The first of base_1, base_2, … that no constraint in used holds, which then holds it, as PostgreSQL’s ChooseConstraintName chooses a name with an empty label for a base that a constraint of the schema already holds.
foreign_key_provenance_matches: Attachment provenance tracks one local row even after its name or enforcement flags change. Legacy entries may still lack the independent catalog identity.
foreign_keys_match_without_object_id
materialize_check_identity: StoreRelCheck: a CHECK constraint takes its incarnation and its pg_constraint OID when it is stored and keeps them afterwards.
materialize_column_key_constraints
materialize_constraint_metadata
materialize_constraint_metadata_with_names: Validate explicit local names before excluding schema-wide names from automatic selection.
materialize_foreign_key_identity: CreateConstraintEntry for a foreign key: the constraint row’s incarnation and OID, allocated when the constraint is created and kept afterwards.
synchronize_partition_inherited_foreign_key_ids