You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We’re actively using Citus + Patroni with multiple "citus-enabled" databases in production and would really like to be able to use the new Citus integration with Patroni in our setup. Currently this integration only supports clusters with a single "citus-enabled" database which prevents us from using the new functionality.
The text was updated successfully, but these errors were encountered:
We would be very interested in using multiple Citus enabled databases with Patroni as well.
I am not currently familiar with the codebase but if there is something we could do to help move this forward, let me know.
Usually people create many databases in a single cluster because they are small or because the host where cluster runs has a lot of hardware resources. In both cases it is about efficiently utilizing resources.
Citus solves a different problem. You have a lot of data so it doesn't fit into a single machine and you want to spread this data across many of machines.
Therefore, creating multiple databases (especially so many) with a Citus extension is an antipattern. Either you have to few data and you don't need Citus, or you better run multiple Citus clusters, with one DB per cluster.
In other words, this feature will never be a top priority.
Describe the feature request
We’re actively using Citus + Patroni with multiple "citus-enabled" databases in production and would really like to be able to use the new Citus integration with Patroni in our setup. Currently this integration only supports clusters with a single "citus-enabled" database which prevents us from using the new functionality.
The text was updated successfully, but these errors were encountered: