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

Add an option for using Timescaledb and not Postgres partitioning #46

Open
mkaranasou opened this issue Aug 29, 2020 · 0 comments
Open
Assignees

Comments

@mkaranasou
Copy link
Collaborator

Since we've currently moved to Timescaledb and abandoned Postgres partitioning, we need to add this to the flow, so that every time a database is created, the user can chose between the two.

So instead of the partitioning script, after request_sets has been created, we need to run:

-- https://github.com/timescale/timescaledb/pull/61/commits/aecd681062e2710b861299b4f0aaaf1fa5eeef0b
SELECT create_hypertable('request_sets', 'stop', if_not_exists => true);
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant