retrofit
0.13.0
retrofit.sh

Advisory codes

Every advisory retrofit prints, by code. The register is the word a text line opens with and the JSON level: warning or note. A braced name such as {table} is a value the printed line fills in. A message that varies with a field shows each form on its own line, led by the field’s value. Where the message is only such a value, its detail and hint lines follow it.

CodeClassRegisterMessage
adopted-default-data-rootschemawarningadopting the default data corpus root {path}, which already holds data files that no schema of this project owns, or that cannot be read as this project’s
after-traffic-outcomedata-motionnote{operator} {opid} meets rows that traffic wrote after it
already-pinneddmlnote{path} already anchors on {opid}; nothing was written
apply-risk-add-excludeapply-riskwarningadding an EXCLUDE constraint builds its index and checks every row under an exclusive lock, and PostgreSQL has no concurrent form; on a populated table run it in a window that can hold the lock
apply-risk-add-not-nullapply-riskwarningSET NOT NULL scans the table under an exclusive lock; on a populated table add a NOT VALID CHECK (col IS NOT NULL) in an earlier migration, then VALIDATE it and SET NOT NULL to avoid the long lock
apply-risk-add-uniqueapply-riskwarningadding a UNIQUE constraint builds its index under an exclusive lock; on a populated table CREATE UNIQUE INDEX CONCURRENTLY first, then ADD CONSTRAINT … USING INDEX to avoid the long lock
apply-risk-data-corpusapply-riskwarning{table}: some rows are not owned by this schema
apply-risk-data-droppedapply-riskwarninghistory-bound, unroutable-purpose, not-selected, superseded, table-dropped, table-filtered, undeclared, table-joined, table-split, table-merged, table-inlined, table-unjoined, reference-data: {table}: {exclusion_cause}: some rows cannot be applied by this run
ddl-only: {table}: some rows are excluded from the captured data
apply-risk-data-exclusionsapply-riskwarninghistory-bound, unroutable-purpose, superseded, table-dropped, table-filtered, undeclared, table-joined, table-split, table-merged, table-inlined, table-unjoined, reference-data, ddl-only: {table}: some rows are excluded from the captured data
not-selected: {count} dataset(s) not named ({table_count} table(s)); name them with --label, or run retrofit data list to see what is present
apply-risk-data-exclusions-tableapply-risknotehistory-bound, unroutable-purpose, not-selected, superseded, table-dropped, table-filtered, undeclared, table-joined, table-split, table-merged, table-inlined, table-unjoined, reference-data: {table}: {exclusion_cause}: some rows did not reach the emitted band
ddl-only: {table}: some rows are excluded from the captured data
apply-risk-data-not-reversedapply-riskwarningdown-not-reversed: {table}: {down_cause}: preserved DML is not reversed by --down
no-fold-at-target: {table}: {down_cause}: the reference table has no fold at the target; its rows are kept
apply-risk-database-atapply-risknoteschema {schema}: apply-risk is judged from the database cut {opid} (pinned by {name})
apply-risk-database-at-behind-sealapply-risknoteschema {schema}: apply-risk is judged from the database cut {opid} (pinned by {name}), which precedes the latest Seal; tables created, and names given, after it and at or before that Seal are judged new, which holds only if the database’s next run goes from the pin past this op
apply-risk-database-at-ignoredapply-risknotethe database-at pin is ignored here, which resolves none: {name}
apply-risk-exclusive-lockapply-riskwarning{operator} {opid} moves rows under an EXCLUSIVE lock on {table} held to COMMIT, blocking writes and foreign-key checks for the whole move
apply-risk-import-summaryapply-riskwarningthe import carries {count} apply-risk advisories
apply-risk-matview-refresh-costapply-riskwarning{table}: refreshing this materialized view is not free
apply-risk-partition-tree-locksapply-riskwarning{operator} {opid} locks over 1,000 relations in one transaction
apply-risk-recorded-unsealedapply-risknotenames recorded into the unsealed tail are read by apply-risk as unreleased and new
apply-risk-rename-in-useapply-riskwarningtable: renaming table “{name}” breaks readers still using the old name
column: renaming column “{name}” breaks readers still using the old name
apply-risk-share-row-exclusive-lockapply-riskwarningvalidating foreign key on a populated table acquires SHARE ROW EXCLUSIVE lock for the scan, blocking writes
apply-risk-table-rewriteapply-riskwarningCastColumn {opid} changes the type of {columns} on {table} under an ACCESS EXCLUSIVE lock
apply-risk-validating-checkapply-riskwarningvalidating CHECK constraint scans and locks the table; author it as NOT VALID (not_valid=true) then VALIDATE CONSTRAINT in a later migration (separate transaction) to avoid the long lock on a populated table
apply-risk-validating-fkapply-riskwarningvalidating FOREIGN KEY scans and locks the table; author it as NOT VALID (not_valid=true) then VALIDATE CONSTRAINT in a later migration (separate transaction) to avoid the long lock on a populated table
apply-risk-view-rebuildapply-riskwarningReplaceView of {target} renders as a rebuild: {reason}
apply-risk-window-add-not-nullapply-riskwarningschema {schema}: op {opid} sets NOT NULL on a column of {table} inside the migration window; the scan runs under an exclusive lock on a table that may hold rows
apply-risk-window-unsealedapply-risknoteschema {schema}: no Seal, so the migration window begins at root and {table_count} tables in it were treated as newborn (empty); seal what production carries so the apply-risk gate can see it
apply-risk-window-validating-checkapply-riskwarningschema {schema}: op {opid} validates a CHECK constraint on {table} inside the migration window; the scan locks a table that may hold rows
apply-risk-window-validating-fkapply-riskwarningschema {schema}: op {opid} validates a FOREIGN KEY on {table} inside the migration window; the scan locks a table that may hold rows
apply-risk-withheld-newbornapply-risknotenewborn: schema {schema}: apply-risk withheld for table {name}, created at {opid} and not populated since (judged from {reason})
rename: schema {schema}: apply-risk rename withheld; old name {name} is absent at F (judged from {reason})
atomicity-segment-boundary-crossedatomicitywarning{opid}: this migration spans more than one transaction
atomicity-wrapper-suppressedatomicitywarningno BEGIN;/COMMIT; wrapper was emitted for this file
boundary-requirement-commit-boundaryatomicitywarning{operator} needs a transaction boundary that --envelope={target} leaves to the apply context
boundary-requirement-non-transactionalatomicitywarning{operator} needs a transaction boundary that --envelope={target} leaves to the apply context
cascade-non-atomic-on-no-transactionatomicitynoteChangePrimaryKey appended with N={count} dependent FK rewrite(s); cascade must run inside one transaction to apply atomically (the default --envelope=own wrap satisfies this; --envelope=caller and --envelope=independent emit no wrapper, so the apply context must supply one)
change-primary-key-non-atomicatomicitywarningcascade may apply partially: no BEGIN/COMMIT wrapper was emitted under --envelope={target}
column-narrowing-breaks-dependentschemawarning{target} reads {columns} of {name}, which the ReplaceView no longer holds, so the migration’s re-create of {target} fails at apply
corpus-file-skippedschemawarningskipped malformed corpus file {path}
corpus-foreign-records-presentapply-riskwarningunregistered-owner: {count} record(s) under this corpus root are owned by other schemas: {owning_schemas}
zero-owned: no record under this corpus root is owned by this schema; all {count} belong to: {owning_schemas}
corpus-records-owned-by-other-schemaapply-risknoteother-schema: {table}: {count} record(s) under this corpus root are owned by schema {schema}
unregistered-schema: {table}: {count} record(s) under this corpus root are owned by no registered schema
corpus-rollback-incompleteschemawarningrollback of {name} failed
data-file-missingdata-motionwarningthe data record for {table} at {opid} ({path}), in the range this down reverts, is named by a witness, but no file carries it
data-file-unaddressedschemawarning{path} is not an addressed data file and was not checked
data-file-unfilledschemawarningunfilled data file {path}: it declares body=data but holds no records, or a record still carrying scaffold placeholders
data-layer-below-floordmlnote{label} contributes to {table} at {contribution-anchor}, below the {lower-floor-kind} body={lower-floor-body} floor {lower-label} placed at {lower-floor-anchor}
data-loss-on-applyschemawarning{reason}
hint: matview-cache, null-key-rows, unreferenced-lookup-rows: capture the affected rows before applying, or re-shape the change to preserve them
hint: drop-or-cast: capture the affected rows before applying, or re-shape the change to preserve them; under migrate --down, restore them from a backup taken before that op applied
data-loss-on-apply-narrowing-castschemawarning{table}: narrowing cast from {from_type} to {to_type} may lose data on apply
data-loss-on-apply-render-chosenschemawarningthe reverse of {operator} {opid} loses the rows of {name} ({grade})
data-motion-cascade-scopedata-motionnote{reason}
data-motion-copy-post-fork-independencedata-motionnotethe copy and {table} are independent identities from this op forward; post-op edits to either table do not propagate to the other
data-motion-declaration-inheriteddata-motionnote{table} is reference data because its source {target} is declared; if its rows are not reference data, withdraw it with retrofit schema ref-tables remove --schema {schema} {table}
data-motion-deferred-splitdata-motionnote{table}: {count} split candidates deferred to a later batch
data-motion-fresh-sequencesdata-motionnote{reason}
data-motion-keyed-folddata-motionnote{operator} {opid} folds each inlined source’s columns and rows into {table} along their primary keys and drops the sources; the inlined columns take the survivor’s privileges and an inlined source’s grants end with it
data-motion-partition-not-pg-declarativedata-motionnoteSplitTable is a row-axis split that moves rows into new tables and keeps its source; it does NOT emit PARTITION BY / PARTITION OF declarative-partitioning DDL
data-motion-product-capture-oweddata-motionnote{table} is reference data (declared source {target}), and the rows this op gives it exist only in migrated databases: capture {table} at HEAD (retrofit data capture <dump> --table {table}, then retrofit data witness) before op seal, which refuses reference-rows-uncaptured until then
data-motion-replica-columndata-motionwarninga snapshot proof writes {columns} into every row of {table}, so a logical-replication subscriber whose copy lacks the column stops applying at this transaction
data-motion-source-consumeddata-motionnote{count} source(s) end at this op; {table} stays and takes their rows; snapshot DDL stops emitting the sources from this opid forward
data-motion-triggersdata-motionnote{operator} {opid} writes rows the triggers listed here fire on; the render toggles no trigger
data-only-single-statement-autocommitatomicitynotethis --data-only band applies as individually autocommitted statements at {opid}: an abort mid-band leaves every completed phase committed
data-qualifieddmlnoterecord seq={seq}: the renderer qualified {qualified_sites}
data-replace-cascadedmlwarningreaching: replacing {table} at {opid} reaches into {name}, which this slot does not replace ({reason})
blocking: replacing {table} at {opid} may be blocked by rows in {name}, which this slot does not replace ({reason})
reaching_ref: replacing reference table {table} at {opid} reaches into {name}, which this slot does not replace ({reason})
blocking_ref: replacing reference table {table} at {opid} may be blocked by rows in {name}, which this slot does not replace ({reason})
cross_slot: replacing {table} at {opid} acts on {name}, which is replaced in a different slot of this script ({reason})
keyed_child: clearing {table} at {opid} meets rows in {name}, whose keyed staged block retains them through the clear ({reason})
self: replacing {table} at {opid} acts on its own self-referencing foreign key ({reason})
data-replace-crossingdmlwarningreference table {table} (floor at {opid}) is written as a delta because this range crosses the removal of its declaration at {name}; rows the corpus never held are kept ({reason})
data-replace-prologuedmlwarning{table} is replaced by its full observed state at {opid} ({reason})
data-replace-unordereddmlnotethe foreign-key graph could not be read at {opid} ({reason}), so the prologued tables ({values}) are emitted in the stated tie-break order
data-replace-whole-reloaddmlwarningreloading {table} whole; {values} are not carried by the body and will be set to NULL
data-statement-order-fkdmlwarningstate-before-statement: the rows that state {table} load before the statements that supply {target} ({name})
child-statements-first: {table}’s statements run before {target}’s under {name}
data-witness-mismatchdata-motionwarningthe data record for {table} at {opid} ({path}), in the range this down reverts, no longer matches its witness
data-witness-missingdata-motionwarningthe data record for {table} at {opid} ({path}), in the range this down reverts, has no witness in the covering seal’s range
database-at-op-revisedapply-risknoteschema {schema}: op {opid} at or before the database-at pin is no longer held as applied; the pinned database applied it (a working copy to rebuild)
database-at-unresolvedapply-risknoteschema {schema}: the database-at pin {reason} (from {name}) does not resolve; the declared database’s cut is unread, so apply-risk withholds nothing
deferred-keys-bracketeddata-motionnotethe script sets the INITIALLY DEFERRED foreign keys of the ops that write rows immediate for each op and returns them to deferred
deferred-keys-oweddata-motionwarningthe script writes rows under INITIALLY DEFERRED foreign keys and sets no constraint mode; under --envelope caller the enclosing transaction owes it
deferred-keys-pendingdata-motionwarningdata record seq={seq} leaves foreign-key checks on {schema}.{table} queued when op {operator} {opid} alters the table; that op fails 55006 (pending trigger events)
deferred-trigger-oweddata-motionwarningthe script’s writes leave events of the deferred constraint trigger {schema}.{name} queued on {table} when op {operator} {opid} alters the table; that op fails 55006 (pending trigger events)
deferred-trigger-pendingdata-motionwarningdata record seq={seq} leaves events of the deferred constraint trigger {schema}.{name} queued on {table} when op {operator} {opid} alters the table; that op fails 55006 (pending trigger events)
dml-behind-windowdmlwarningroot-boundary: DML seq={opid} purpose={purpose} anchored on the pre-genesis root boundary is behind --from; omitted
named-opid: DML seq={opid} purpose={purpose} anchored on {name} is behind --from; omitted
sealed-opid: DML seq={opid} purpose={purpose} anchored on {name}, inside seal {target}, is behind --from; omitted
dml-body-meta-command-admitteddmlwarning{name} was emitted into the artifact under --allow-unscreened-dml; psql runs it client-side, outside retrofit’s transaction framing — a session command such as \connect ends the transaction open before it
dml-body-partition-dependentdmlwarning{name} cannot run inside a transaction block when its target relation is partitioned, and retrofit does not read the database catalog; if the target is partitioned, this window applies as one more segment than reported
dml-chain-near-missdmlwarning{reason}
hint: re-run with the prior label-set (or hand-edit the labels) if this was meant to supersede
dml-dump-band-listeddmlwarning{count} rows listed, not captured: {table}
dml-op-show-matview-replacedmlnotereplacing materialized view {name} discards its stored rows
dml-purpose-unclassifieddmlnotetransition: {opid}: DML is classified as a transition
seed: {opid}: DML is classified as a seed
cleanse: {opid}: DML is classified as a cleanse
unclassified: {opid}: DML carries no purpose classification
ref: {opid}: DML is classified as reference data
dml-ref-table-flag-ignoreddmlnote{name} ignored: {table} is a declared reference table, so its record is purpose=ref
dml-ref-table-no-match-universedmlnoteschema {name} has no ops at HEAD, so no pattern can match yet
dml-ref-table-policy-disagreementdmlwarning{count} tables carry committed records their reference-data declaration would classify differently
dml-ref-table-seed-dormantdmlnoteseed[{seed-labels}] holds {table} ({opid}); kept, never reclassified, and dormant while {table} is reference data
dml-seed-band-opt-in-requireddmlwarningrecords in a purpose=seed file apply only{reason}; without it they are excluded and counted
dml-superseded-in-windowdmlwarning{name}: a superseded reference record is needed by a step before the floor this run mints; the window from the last Seal will refuse
dml-unclassified-listeddmlwarning{count} records unclassified: {table}
drift-convert-recognition-gatedschemanotepartition-convert recognition inactive
drift-extract-unrecognizedschemawarningextract-shaped reshape not recognized as an ExtractTable
drift-fk-facet-recaptureschemawarningthis recreate reconciles referential-action facets that differ between the oplog and the database; capturing them converges in one pass and does not recur
drift-merge-shape-mismatchschemawarningmerge sources differ on a compared field
drift-move-column-candidateschemawarninga column dropped from one table and added to another was not recognized as a MoveColumn
drift-skip-internal-defectschemawarningdrift skip {skip_kind} on {name} in schema {schema} (line {line}) is a retrofit defect: valid PostgreSQL does not reach it with the pinned parser
drift-skip-unclassifiedschemawarningunclassified drift skip {skip_kind} on {name} in schema {schema} (line {line}): {reason}; retrofit has no class for this skip, so it counts as a gap
drift-split-unrecognizedschemawarningsame-shape table beside a surviving source was not recognized as a SplitTable
drift-survivor-extract-unrecognizedschemawarningcolumn extract off surviving table {table} was not recognized as an ExtractTable
drop-opaque-readersschemawarningtable: dropping table “{name}” leaves function bodies retrofit cannot read; any may still use it
column: dropping column “{name}” leaves function bodies retrofit cannot read; any may still use it
function: dropping function “{name}” leaves function bodies retrofit cannot read; any may still call it
element-ref-absentschemawarningthe element {element_id} has no ref that binds it under every operator that takes its kind
enum-value-commit-boundarytypenotethe new value {name} on {target} is not usable until the adding transaction commits
excluded-schema-referencedschemanotekept statements reference objects of the excluded schema {name}; each keeps the disposition a reference into an unmanaged schema has
exclusion-appliedschemanote~ (excluded) {excluded_kind} {name} — {count} statement(s) — {reason}
experimental-graduatedschemawarning[experimental] purposes lists {name}, which is no longer experimental
experimental-purposedmlwarning{path}: purpose={purpose} records are experimental: a released record is protected only by its position in the log, not by a Seal’s digest
extract-rejoin-key-addeddata-motionnotethe extract added rejoin keys that appear in no oplog text
extract-rejoin-key-no-delete-actiondata-motionnote{operator} {opid} ties each child to {table} by a rejoin foreign key with no ON DELETE action, and its forward gives every {table} row a child row: a {table} row that has one can no longer be deleted
extract-reverse-guard-non-atomicatomicitywarninga guard in this script is not atomic with the changes before it: no BEGIN;/COMMIT; wrapper was emitted under --envelope={envelope}
extract-reverse-ordinal-divergencedata-motionnoteextract-reverse-ordinal-divergence
extract-survivor-arm-selecteddata-motionnotesource table {table} survives this extract in place
from-dump-seal-rundmlnotethe dump matches a run of seals joined only by ops not observable in a schema-only dump
gitattributes-missingschemawarning.gitattributes is missing the {config_path} line
import-force-orphaned-referencesschemawarningschema {schema}: {count} bodies reference elements no registered schema resolves after this --force: {values}
internal-advisory-write-failedinternalwarningan advisory could not be written to its channel: {reason}
internal-invalid-advisoryinternalwarningzero-def: advisory definition {original_code} is incomplete and cannot describe itself
undeclared-field: advisory definition {original_code} was supplied a field it does not declare
missing-field: advisory definition {original_code} is missing a value for a field it declares
container-mismatch: advisory definition {original_code} was supplied a value at the wrong container kind
off-token-discriminator: advisory definition {original_code} was supplied a discriminator value outside the closed token set it declares
internal-reserved-type-violationinternalwarningrecord type {type_name} is reserved for the advisory carrier and cannot be emitted through the generic {entry_point} writer
join-key-demotedschemanoteJoinTable carries primary key {name} ({element_id}) onto {table} as UNIQUE: {reason}; kept key {target}
label-duplicateddmlnotelabel {label} was named more than once; the repeat was dropped and the layering is unchanged
label-unmatcheddmlwarninglabel {label} matched no data records; nothing was rendered for it
legacy-origin-defaultschemanotea column’s stored default is a different spelling of the authored default
migrate-segmented-non-atomicatomicitywarning{reason}
hint: apply it with a runner that does NOT open its own transaction (plain psql -f); under --envelope=own a runner wrapping the file in one transaction is refused by name at the head (own-envelope-transaction-open) before any DDL
move-column-down-refuseddata-motionnotemigrate --down refuses a window holding this MoveColumn (migrate-move-column-needs-default): the moved column is NOT NULL with no DEFAULT
owned-sequence-name-staleschemawarninga skipped statement leaves the owned sequence name {name} of {table}.{column} stale
privileges-not-restoredschemawarningview-replace: view {name} is dropped by the preceding DropView and created again by this CreateView: privileges on {name} are not restored
unjoin-child: the UnjoinTable child {name} takes its source’s name: the source’s privileges on {name} are not restored onto it
reference-chain-unfoldabledmlwarningreference chain {table} does not fold offline: {reason}
reference-declaration-unjudgeddata-motionnoteop {opid} combined declared and undeclared tables into {schema}.{table} ({values} not declared), and no judgment records whether it is reference data; record one with retrofit schema ref-tables add --schema {schema} {table} or retrofit schema ref-tables remove --schema {schema} {table} before op seal, which refuses reference-declaration-unjudged until then
reference-key-lostdmlwarningreference table {table} lost {count} key(s) since its chain: {name}
reference-restate-authoreddmlnotereplace: reference table {table}: a hand-written restate states the whole table and renders as a replace
bodies: reference table {table}: a hand-written restate holding a statement other than an INSERT keeps its bodies: migrate renders it as written, not as a replace, and applying it again can fail on rows it already wrote
mint: reference table {table}: a hand-written restate states the whole table and, while its block holds INSERTs only, renders as a replace
layered: reference table {table}: a hand-written restate under a label renders as a replace only while its block holds INSERTs only and no lower layer migrate selects holds the table; otherwise it renders as written, and applying it again can fail on rows it already wrote
reference-table-emptieddmlwarningreference table {table} was observed empty: the replace body=none removes every row
rename-opaque-readersschemawarningtable: renaming table “{name}” leaves function bodies retrofit cannot read; any may still use the old name
column: renaming column “{name}” leaves function bodies retrofit cannot read; any may still use the old name
render-skip-element-not-renderedrender-skipwarningview-body: {name} {element_id} omitted from snapshot: its body cannot be reconstructed without a live catalog
element-body: {name} {element_id} omitted from snapshot: its body references an element not live as of the cut
unsupported-node: {name} {element_id} omitted from snapshot: an unsupported node in its body could not be rendered
reverse-declared-noopatomicitynoteRunRawScript {opid} contributes nothing to the down: it declares no down action is needed ({reason})
reverse-guardatomicitynotecheck: {operator} {opid} returns the check on {name} as a guard
rule: {operator} {opid} returns the rule on {name} as a guard
reference-edge: {operator} {opid} returns the reference edge on {name} as a guard
reverse-irreversibleatomicitynotepaired: {name} is paired, not the element the target held: its rows left with the drop
not-null-not-restored: {name} comes back nullable: its NOT NULL is not restored
holder-child: {name} is rejoined as the holder child, not the element the target held
matview-unpopulated: {name} is re-created WITH NO DATA, unpopulated until its REFRESH
synthesized-name: {name} is synthesized from a new ElementID, not the name the target’s cut renders
re-minted-name: {name} is re-minted by the key change, not the name the target’s cut renders
order-not-restored: {name} keeps the column order the down leaves: its order is not restored
identity-absent-not-restored: {name} keeps the identity the down leaves absent: its identity is not restored
re-created-empty: {name} comes back empty: its rows left with the drop
reverse-leg-heldatomicitynotetable {table} already holds the fold the down would restore, so the reference leg leaves it
reverse-noopatomicitynoteleft-validated: {name} is left validated: its validation contributes nothing to the down
left-not-valid: {name} is left NOT VALID by its declared policy: it contributes nothing to the down
reverse-opaqueatomicitynoteRunRawScript {opid} reverses by its declared reverse_body, verbatim and unchecked
reverse-recordedatomicitynotethe range {target} is already recorded by ops {name}; what remains reaches {opid}
reverse-sliceatomicitynotethe reverse is a slice to {opid}; {count} later operations are kept
reverse-stopatomicitynote{operator} {opid} stops the reverse
reverse-undeclaredatomicitynoteRunRawScript {opid} declares no reversal: a down over it refuses until it declares one of reverse_body, reverse_blocked or reverse_noop
reverse-unrecordedatomicitynotethis script is unrecorded: the oplog does not record the reverse it applies
reverse-withdrawnatomicitynoteDeclareReversal {opid} withdraws DeclareReversal {supersedes} for RunRawScript {target}: the script’s inline {reversal_arm} now governs the down
reverse-writes-before-ruleatomicitynote{operator} {opid} relaxes the rule on {name} in {table} after earlier ghost ops wrote rows
row-axis-reportdata-motionnote{operator} moves rows of {table}: {query}
schema-body-findingschemawarning{name}: {opid} {diagnostic}: {reason}
schema-contextschemanote{schema}
schema-deprecated-flagschemawarning--as={name} is deprecated for op show; use --framing={name} and the persistent --as=text|json for output mode
schema-drift-observedschemawarningadded: {target} exists in the database but not in the schema
removed: {target} exists in the schema but not in the database
modified: {target} differs between the schema and the database
renamed: {target} appears renamed between the schema and the database
unmodelled: {target} carries a facet the model does not represent
unresolved: {target} could not be resolved against the schema
deferred: {target} was deferred to a later drift pass
schema-emission-sentinelschemawarningemission-path sentinel ({name})
schema-fork-unmergedschemawarningschema {schema}: {values} share prev={opid}; the oplog carries an unmerged fork
schema-import-drop-moved-past-reader-replaceschemanotethe drop of {target} was minted after the CREATE OR REPLACE FUNCTION at line {line} that ends its read by {reason}
schema-import-index-key-expression-unresolvedschemawarningindex {name} in schema {schema} was set aside: its key expression could not be resolved ({reason})
schema-import-reader-drop-moved-aheadschemanoteDropFunction {name} was minted ahead of the drop of {target} at line {line}, which it read; this DROP FUNCTION mints nothing
schema-import-skip-reviewschemanotesome objects were set aside during import
schema-import-unclassified-kindschemawarningan object kind reached the classifier with no matching arm
schema-init-flag-ignoredschemawarning{name} ignored
schema-occupancy-undeterminableschemawarning{reason}
schema-op-show-replay-findingschemawarningreplay could not classify every op in this oplog
schema-partition-bound-timestamptz-zonelessschemawarningpartition {name} bounds a timestamptz key by {values} with no UTC offset
schema-partition-tree-indexedschemawarningpartitioned table {table} holds an index, so identify and migrate --from-dump cannot place a database holding its partition tree
schema-policy-references-unmodeled-roleschemawarningpolicy {name} references role(s) {values} that retrofit does not track; verify they exist before apply
schema-registry-emptyschemanoteno schemas are registered under {schema}
schema-same-operator-as-tailschemawarning{operator} on lines {values}
schema-stray-oplogschemawarning{path}
seal-avoidable-lossschemanote{operator} {opid} on {name} ({element_id}) loses data that a later op of this range gives back without it
seal-avoidable-loss-unreadschemawarningthe corpus scan failed, so this range’s avoidable losses were not read
seed-anchor-sealeddmlnote{table} record anchors on {opid}, inside the range seal {target} covers: a fresh build and --at render it there; a database already past seal {target} will not receive it (migrate --from {target} omits it, dml-behind-window)
sequence-not-created-by-renderschemawarningsequence {name} that {table}.{column} draws from is not created by the rendered DDL
sequence-reference-unparsedschemawarningthe DEFAULT of {table}.{column} calls nextval on a sequence the rendered DDL may not create
snapshot-state-under-triggerdata-motionnotethe rows that state {table} load before trigger {name} exists and do not fire it; migrate --from root loads them with {name} live
split-table-down-refuseddata-motionnotemigrate --down refuses a window holding this SplitTable: the split moved rows, and its reverse is a MergeTable you author
squash-lossy-stepschemanote{operator} {opid} on {name} is taken out, and a database past it has already lost those values
squash-stopatomicitynote{operator} {opid} stops the squash
stale-dml-referencedmlwarning{reason}
table-pattern-unmatcheddmlwarning--table pattern {name} matched no statement in the source
type-cast-breaks-dependent-calltypewarning{target} passes {columns} to {name}, and PostgreSQL has no implicit cast from {from_type} to the parameter’s {to_type}, so the migration’s re-create of {target} after the cast fails at apply
type-cast-session-time-zonetypenote{target} cast from {from_type} to {to_type} with no using= converts each value in the applying session’s TimeZone
type-creation-onlytypewarningtype “{name}” is a serial pseudo-type usable only when creating a column; it is not a valid ALTER COLUMN … SET DATA TYPE target
type-fk-partner-narrowertypenote{target} stays {from_type} across foreign key {name} from a column cast to {to_type}
type-unknowntypewarningtype “{name}” is not a recognized PostgreSQL built-in type
type-varchar-without-lengthtypewarningwarning: type “{name}” without an explicit length is equivalent to text
suggestion: consider giving type “{name}” an explicit length
validity-cannot-un-validateschemawarning{name}: the reverse of this change cannot re-validate {from_type} against {to_type}
witness-digest-unsupporteddata-motionwarningthe data record for {table} at {opid} ({path}), in the range this down reverts, has a witness whose digest algorithm is not supported
witness-out-of-rangedata-motionwarningthe data record for {table} at {opid} ({path}), in the range this down reverts, has a witness outside the seal range that covers it

Before 1.0, any release may change behavior; the release notes list what changed.

Published .