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

[WIP] Redesigning the hypertable for compression and similar features #44

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

noctarius
Copy link

@noctarius noctarius commented Feb 24, 2023

This PR is a work in progress to test and work on a redesign of the timescale part of the implementation. The main focus is to minimize disk space consumption, increase the compressibility of the table and apply some general best practices.

This PR may eventually resolve #25

@noctarius noctarius marked this pull request as draft February 24, 2023 14:27
@noctarius noctarius force-pushed the master branch 29 times, most recently from bf980ef to e74c823 Compare March 2, 2023 17:10
@noctarius noctarius force-pushed the master branch 19 times, most recently from 6133a28 to a146ffc Compare March 3, 2023 13:11
@freol35241
Copy link
Owner

@noctarius

I can see that you are putting a lof of effort in this and I am grateful for that. But just to be clear, removing the id column is a definitive yes from my side whereas the separate table/ltree approach to the attributes is interesting but merging of it is highly dependant on the complexity introduced to the codebase.

@noctarius
Copy link
Author

Which is fair. No worries on that. The complexity is fairly low, as you can see from the code changes. Happy to fork it out if you don't want to deal with it. I'm basically doing it for myself. Even though I hate Python 😅

@noctarius noctarius force-pushed the master branch 2 times, most recently from 08c9747 to f73e065 Compare March 3, 2023 15:05
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.

Include support for more TimescaleDB features
2 participants