Gabriele Bartolini

> Also, unclear what you mean by "with synchronous replication in place"? How would I enable that? https://cloudnative-pg.io/documentation/current/replication/#synchronous-replication

> Sounds good. > > Please take a look at the cla: [#12403 (comment)](https://github.com/kubernetes-sigs/cluster-api/pull/12403#issuecomment-3005512076) > > We can't merge without it Done, thanks!

Version 1.25 introduced support for logical subscriptions, which simplifies the process of performing major upgrades using logical replication. Additionally, we've added the ability to perform [parallel dump and restore](https://cloudnative-pg.io/documentation/current/database_import/#customizing-pg_dump-and-pg_restore-behavior), providing...

> > one approach for an initial implementation could be an offline update. If the update fails, the system would revert to the previous PostgreSQL version, resulting in an inconsistent...

This feature will be in 1.26.0.

> Hey maintainers let me know if there's something to be added more here! Can you please integrate the documentation? https://cloudnative-pg.io/documentation/current/database_import/#customizing-pg_dump-and-pg_restore-behavior

Thank you for opening this ticket and for your time spent investigating. We will look into this and check all timeouts. FWIW, we highly discourage running the controller on the...

> [@gbartolini](https://github.com/gbartolini) Thank you for your reply. If you need anything else from me just let me know. I believe you saw also the other ticket with a feature request...

Relying on Kubernetes for consensus is a fundamental design choice that sets CloudNativePG apart from other operators, such as Patroni, which depend on a proxy application to manage the cluster....

What are you trying to achieve? `pgstattuple` is already there.