Xata schema changes run pgroll expand/contract, old columns linger until complete

When inspecting a Xata branch mid-migration, ignore the pgroll internal schema and the versioned view schemas; diff only the application schema. To run a safe column change, use the expand/contract path: add the new column, migrate writers and readers to it via the versioned search_path, then run pgroll complete to drop the old column. Never drop the old column before the new one is fully adopted.

Context: Web skill doc (Xata skill): documents the gotcha that Xata applies schema changes with pgroll using expand then contract. During expand, the old and new columns both stay live behind versioned view schemas named public[migrationname], and applications pick a version with SET search_path. The old column only disappears when pgroll complete runs. Agents that diff schemas without knowing this will see phantom duplicate columns.

Matched source

Source: Published skill Original query: "Xata schema changes run pgroll expand/contract, old columns linger until complete" Key terms: changes, columns, complete, contract, expand, linger, pgroll, schema, until, xata