Forum Discussion
Table-level reseed for Mirrored Azure Database for PostgreSQL after DDL change
Hi,
Today, a DDL change on a mirrored PostgreSQL table (for example ALTER COLUMN TYPE) is unsupported and the only recovery is Stop then Start replication on the whole mirrored database, which reseeds every table from scratch. On large databases this is very costly.
The Azure SQL Database, Azure SQL Managed Instance, and SQL Server 2025 connectors already support table-level reseed, where only the impacted table is reinitialized.
Would it be possible (is it already planned?) to bring the same table-level reseed behavior to the Azure Database for PostgreSQL connector via azure_cdc, so a schema change on one table reseeds only that table and leaves the rest of the mirror running?
Thanks!
Currently, table-level reseed is not supported for Mirrored Azure Database for PostgreSQL.
For PostgreSQL mirroring, schema changes that aren't supported by the replication engine (such as certain ALTER TABLE operations like changing a column's data type) require stopping and restarting mirroring. This causes a full reseed of the mirrored database, rather than reinitializing only the affected table.
The table-level reseed capability that exists for Azure SQL Database, Azure SQL Managed Instance, and SQL Server 2025 connectors has not yet been extended to the PostgreSQL (azure_cdc) connector.
At this time, there is no publicly announced roadmap or timeline for bringing table-level reseed to PostgreSQL mirroring. If this functionality is important for your workloads—especially large databases where a full reseed is expensive—it's worth submitting or upvoting the feature request through the Microsoft Fabric Ideas portal. Customer feedback is one of the primary inputs the product team uses when prioritizing enhancements.
So, as of today:
Table-level reseed: ❌ Not supported for PostgreSQL mirroring.
Recovery after an unsupported DDL change: Stop and Start mirroring, which triggers a full database reseed.
Future availability: No public commitment has been announced; monitor the Fabric roadmap and release notes for updates.
Hopefully, parity with the SQL-based connectors will be added in a future release, but currently the full reseed workflow is the expected behavior.
If this answers your question, please consider accepting it as the solution so it can help others with the same issue. If you found it useful, a Kudos would also be greatly appreciated!
2 Replies
Currently, table-level reseed is not supported for Mirrored Azure Database for PostgreSQL.
For PostgreSQL mirroring, schema changes that aren't supported by the replication engine (such as certain ALTER TABLE operations like changing a column's data type) require stopping and restarting mirroring. This causes a full reseed of the mirrored database, rather than reinitializing only the affected table.
The table-level reseed capability that exists for Azure SQL Database, Azure SQL Managed Instance, and SQL Server 2025 connectors has not yet been extended to the PostgreSQL (azure_cdc) connector.
At this time, there is no publicly announced roadmap or timeline for bringing table-level reseed to PostgreSQL mirroring. If this functionality is important for your workloads—especially large databases where a full reseed is expensive—it's worth submitting or upvoting the feature request through the Microsoft Fabric Ideas portal. Customer feedback is one of the primary inputs the product team uses when prioritizing enhancements.
So, as of today:
Table-level reseed: ❌ Not supported for PostgreSQL mirroring.
Recovery after an unsupported DDL change: Stop and Start mirroring, which triggers a full database reseed.
Future availability: No public commitment has been announced; monitor the Fabric roadmap and release notes for updates.
Hopefully, parity with the SQL-based connectors will be added in a future release, but currently the full reseed workflow is the expected behavior.
If this answers your question, please consider accepting it as the solution so it can help others with the same issue. If you found it useful, a Kudos would also be greatly appreciated!
Current status
- Table-level reseed: Not supported for Azure Database for PostgreSQL mirroring.
- Recovery after unsupported DDL changes: Stop and restart mirroring, which reseeds the mirrored database.
- Public roadmap: Microsoft has not announced a roadmap or ETA for adding table-level reseed package to the PostgreSQL (azure_cdc) connector.
At this time, there is no official Microsoft document to mention that table-level application for PostgreSQL mirroring is planned.
If this helps, ✓ Mark as Kudos | Help Others
