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

TimescaleDB CE Testing #2

Open
beasteers opened this issue Feb 8, 2024 · 1 comment
Open

TimescaleDB CE Testing #2

beasteers opened this issue Feb 8, 2024 · 1 comment

Comments

@beasteers
Copy link

beasteers commented Feb 8, 2024

I realize this is pre-alpha so this is not an urgent issue, but testing this alongside TimescaleDB Community Edition (especially compression features) would be great to have as a "known extension compatability" - especially since branching instead of cloning is even more valuable for the scale of data that Timescale is designed to manage.

Neon's branching looks great, but it only supports Timescale's Apache features (so no compression) which is a no-go for us.

I'll try to update with some initial findings if I find some spare time.

I'm not a postgres expert enough to know if there is a fundamental reason why something like compression or other timescale features would be broken by branching so if anyone knows better, I'd be very interested in the info.

Anyways thanks for the extension, it's very exciting!

@NAlexPear
Copy link
Owner

Thanks for the issue submission! I haven't tested this on any distribution of Timescale at all, but I'd be interested in your initial findings. And I'd certainly welcome PRs for a more robust testing strategy for different versions and distributions of Postgres.

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

No branches or pull requests

2 participants