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.

Sign up for GitHub

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

Jump to bottom

Consider putting raw_messages and physical_timeseries tables in a different database #41

Open

dajtxx opened this issue Jun 13, 2023 · 0 comments

Labels

Collaborator

dajtxx commented Jun 13, 2023

These tables grow very large and are a nuisance when backing up, copying, etc.

Consider putting them in a different database to the tables used for general running.

dajtxx added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment