Open beasteers opened 7 months ago
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.
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!