Current Work and Priorities

Driven by real-world usage and production issues

This roadmap reflects the actual backlog across pgloader, pgcopydb, and pg_auto_failover. Work is prioritized based on production impact and user support. Most items come from real-world usage—edge cases, scaling limits, and operational complexity.

Active Themes

What's being worked on now

pgloader

Migration edge cases

Complex schemas (FKs, generated columns, constraints) break automated migration assumptions

pgloader

Connection & drivers

Connectivity inconsistencies across MySQL, MSSQL, and other sources

pgloader

Parsing / SQL handling

SQL dialect differences and parsing limitations in edge cases

pgloader

PostgreSQL compatibility

Adapting to new PostgreSQL features and type systems

pgloader

Stability & performance

Large migrations expose runtime limits and performance bottlenecks

pgcopydb

Cross-platform migrations

Source and target environments not binary-compatible (cloud, OS, versions)

pgcopydb

Logical replication limits

Constraints of logical decoding vs WAL-based replication

pgcopydb

Upgrade workflows

Automating safe PostgreSQL version upgrades with minimal downtime

pgcopydb

Performance tuning

Throughput and parallelism limits on large datasets

pgcopydb

Operational UX

Complexity in CLI workflows and pipeline integration

pg_auto_failover

Failover behavior

Unexpected HA state transitions and failover edge cases

pg_auto_failover

Configuration

Setup complexity and hidden constraints in cluster configuration

pg_auto_failover

HA edge cases

Replication lag, multi-node coordination, distributed state issues

pg_auto_failover

Upgrades & compatibility

Cluster upgrades and version transitions reliability

pg_auto_failover

Integration

Positioning and interoperability within broader PostgreSQL stacks

What this means

This is not a speculative roadmap. It is a reflection of actual production needs across teams using these tools today. Supporting the projects directly influences what gets fixed, improved, and released next.

How work is prioritized

Production blockers and data-loss risks come first
Paid support tiers move issues forward in the queue
Work is grouped and shipped in quarterly releases
Cross-project improvements are prioritized when they unlock multiple use cases

See support options

Influence the roadmap

Fund the work that matters to you

Support These Projects View Projects