-
Notifications
You must be signed in to change notification settings - Fork 99
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
Remove backfill historical data on compressed chunks #3572
base: latest
Are you sure you want to change the base?
Remove backfill historical data on compressed chunks #3572
Conversation
Allow 10 minutes from last push for the staging site to build. If the link doesn't work, try using incognito mode instead. For internal reviewers, check web-documentation repo actions for staging build status. Link to build for this PR: http://docs-dev.timescale.com/docs-3559-docs-rfc-remove-backfill-historical-data-on-compressed-chunks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
…ata-on-compressed-chunks
@@ -59,6 +59,20 @@ SELECT * FROM timescaledb_information.jobs | |||
For more information, see the API reference for [`timescaledb_information.jobs`][timescaledb_information-jobs]. | |||
## Pause compression policy | |||
To disable a compression policy temporarily: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably tell people how to find the jobid here.
SELECT * FROM timescaledb_information.jobs where proc_name = 'policy_compression' AND relname = ''
|
||
```sql | ||
SELECT * FROM timescaledb_information.jobs where proc_name = 'policy_compression' AND relname = '' | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I wasn't clear, relname would be set to the hypertable name. So however we show that in other places in the docs <hypertablename>
maybe?
No description provided.