Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Citus support #2230

Open
janantos opened this issue Feb 20, 2023 · 5 comments
Open

Citus support #2230

janantos opened this issue Feb 20, 2023 · 5 comments
Labels
discussion question spilo Issue more related to Spilo

Comments

@janantos
Copy link

Is Citus supported in postgres-operator the way it is supported by patroni?

@steven-sheehy
Copy link

steven-sheehy commented Feb 26, 2023

I'm also interested in Citus support after hearing Patroni now supports Citus in its 3.0 release.

@FxKu
Copy link
Member

FxKu commented Mar 24, 2023

It must be supported in Spilo. Then the operator could spin up Postgres cluster with Citus extension. Could be that some config options would need to get introduced then.

@FxKu FxKu added question discussion spilo Issue more related to Spilo labels Mar 24, 2023
@chokosabe
Copy link

Has anyone tried this with Citus? Stackgres using a lot of the same components and they seem to have citus support

@nihaldivyam
Copy link

@FxKu is citus supported ?

@cyraid
Copy link

cyraid commented Apr 16, 2024

According to an issue on the Spilo repo ( zalando/spilo#926 ), Hughcapet responded with "Not in our plans for the nearest feature" on Feb 19th, 2024 and closed the Issue as Completed. I'm not sure how long there will be no support planned for it, but we know there's no plans as of Feb 19th and the 'nearest future' (which may be ambiguous).

Citus support would be nice for those looking to improve their experience with the enhancements that Citus provides, including Multi-Tenancy (which is what I would be needing it for), so I too, am in favour of this addition.

As a guess (speaking with my inexperience with the repo), I wonder if it's because they may not want to support multiple branches of packages (an image with citus and an image without, eg. "spilo-citus", and "spilo"). Any Spilo devs willing to chime in with information? (seeing as both seems to be run by the same organization)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion question spilo Issue more related to Spilo
Projects
None yet
Development

No branches or pull requests

6 participants