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

feat: add columnar db #849

Closed
wants to merge 1 commit into from
Closed

feat: add columnar db #849

wants to merge 1 commit into from

Conversation

riderx
Copy link

@riderx riderx commented Dec 20, 2023

Please go the the Preview tab and select the appropriate sub-template:

@riderx riderx requested review from a team as code owners December 20, 2023 07:42
@olirice
Copy link
Contributor

olirice commented Dec 20, 2023

thank you for opening and the PR looks good

The bar for adding new extensions to the platform is very high as it's a big commitment from us to maintain them indefinitely if the current authors become unavailable. In this case we the extension is fairly new (< 18 months old) and the platform already supports a comparable extension through TimescaleDB's column store. For those reasons, I'm going to close this for now. If we see a big uptick in requests for hydra we can revisit in the future

@olirice olirice closed this Dec 20, 2023
@riderx
Copy link
Author

riderx commented Dec 21, 2023

Thanks @olirice for the quick reply.

I understand your concern, to give some context, Hydra is a company running cloud DB like Supabase.
It's a fork of an older project, citus 7 years old.

Hydra isolated the extension before citus took a direction of Distributed DB, I could have used columnar from citus.

In my point of view (as Supabase cloud client) TimescaleDB is not doing the job, the license prevents any interesting use of TimescaleDB.
https://docs.timescale.com/about/latest/timescaledb-editions/
No compression, no Continuous aggregates, no retention policy, no Actions and automation.

So by adding an alternative, i'm resolving my current issue in Supabase Cloud.

So I would be grateful if you could consider this a bit further.

Columnar is "Next generation of cstore_fdw", using latest best practices of Postgres.

This could open many use cases in analytics for cloud user who cannot use TimescaleDB

I'm open to any alternative I found hydra was more close in philosophy that citus to supabase.

A good alternative could be to use https://pgxman.com/ for extension since it's made for install extension and has hydra listed.

@olirice
Copy link
Contributor

olirice commented Dec 21, 2023

thanks for the links, very interesting read

I think long term we are likely to revisit column storage in addition to timescale. Before we make any decisions we'll need to do an internal review of options that includes:

  • features
  • performance
  • alignment with our products' direction
  • supportability by our tech team
  • supportability by our support team (we handle support for our extensions as well as the supabase platform)

I'll make sure we include hydra in that comparison when we circle back to tackle to it, but its not something we can add for right now

@riderx
Copy link
Author

riderx commented Dec 21, 2023

@olirice okay, i will keep using clickhouse until i can put back my analytics into Supabase.
Thank for considering it !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants