Supported databases and limits
Current PostgreSQL, MySQL 8.4 and MongoDB 8.0 connector scope, with local, S3, Azure Blob and GCS destinations.
PostgreSQL
Supports ordinary non-inherited tables with a single smallint, integer or bigint primary key. Supported scalar values include text, exact numeric, booleans, floats, date/time, UUID and JSON representations. RLS, unsupported types and table shapes fail explicitly. Batch limit is 1,000 rows; transport rows are bounded at 64 KiB. Source SELECT and schema USAGE cover export; deletion adds DELETE and stricter table checks.
MySQL 8.4
Supports InnoDB with a single supported integer primary key, including unsigned BIGINT through 18446744073709551615. Bounded scalar values include exact decimal, text, binary and temporal types; unsupported schema/types fail. Batch limit is 400 rows and native row payload is capped at 30,000 bytes. SELECT and PROCESS are needed for source reads/identity inspection. Use the database name as --schema. MySQL-compatible variants such as MariaDB are not qualified.
coldctl policy create --name mysql-orders --source mysql-source --destination local-archive --schema app --table orders --time-column created_at --older-than-days 365 --batch-size 200MongoDB 8.0
Requires a replica-set primary, ordinary non-capped collections, ObjectId keys, a top-level BSON Date retention field and quiescent-copy throughout archival and resume. Standalone/secondary/router, time-series, capped, clustered and encrypted collections are unsupported. Documents are capped at 30 KiB and batches at 100. Raw BSON is preserved; equality filters and cross-engine restoration are unavailable. The connector needs read/discovery and topology-inspection permissions; read on the database plus clusterMonitor on admin is the fixture role pattern.
coldctl policy create --name mongo-events --source mongo-source --destination local-archive --schema app --table events --time-column created_at --older-than-days 365 --batch-size 100
coldctl archive run mongo-events --source-stability quiescent-copyImplemented and pending
All three connectors support archival, same-engine separate-target restore and explicit verified deletion within their supported shapes. The local scheduler resumes queued work and supports explicit recurring PostgreSQL/MySQL/MongoDB-to-S3/Azure/GCS archive/delete cycles. S3, Azure and GCS sinks and the separate archive gateway are implemented. Mutable-source snapshots, CDC and incremental watermarks remain outside the workflow. Development test coverage does not imply production-scale qualification.