Module composites 

The attribute checks of DefineCompositeType in PostgreSQL’s order: MergeAttributes rejects too many attributes and then a repeated name, BuildDescForRelation resolves each attribute’s type, requires USAGE on it, derives its collation and rejects SETOF, and CheckAttributeNamesTypes then rejects pseudo-types.

Re-exports

pub use crate::catalog::collations::builtin_collation_oid;

Modules

type_changes

Composite attribute type preparation and dependency checks, before any catalog write.

Constants

MAX_ATTRIBUTES

MaxHeapAttributeNumber.

Functions

prepare_added_attribute

ATExecAddColumn for a composite relation, after its owner and kind have been checked.

prepare_composite_attributes

Check and bind the declared attributes of a new composite type, numbering them from one.

type_is_collatable

Whether values of a type carry a collation.

validate_removed_attribute

Resolve a live composite attribute before dependency traversal. Composite relations have no system columns.

validate_renamed_attribute

renameatt_internal checks the source before the destination; standalone composites have no system attributes.