You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current documentation versioning does not seem to work. When selecting "version", the options for latest:2.X works, but 1.7 etc does not work. Also, please don't just remove old doc, people might be using it.
Contributing to documentation
We welcome documentation contributions!
For information about how to propose a change, see the contributing guide in our GitHub repository.
For information on style and word usage, see the style guide
The text was updated successfully, but these errors were encountered:
Was a more complete guide on that link for how to backup and restore to a docker instance of timescale, which was very helpful. The information has since been moved and is scattered around in the docs. Maybe add it as a recipe or something? Useful for restoring old backups that was not done using the same process as described in the new docs.
Use this template for reporting bugs in the docs.
Describe the bug
Missing documentation, old working documentation for pg_dump + restore is gone.
It was located here: https://docs.timescale.com/use-timescale/latest/migration/pg-dump-and-restore/#restore-your-entire-database-from-backup, and linked to from URL in title i am pretty sure of. Without it, old backups are hard to use.
What do the docs say now?
No link for the bulletpoint "Logical backups with pg_dump and pg_restore."
What should the docs say?
Should link to relevant documentation
Page affected
https://docs.timescale.com/self-hosted/latest/backup-and-restore/
Any further info
Current documentation versioning does not seem to work. When selecting "version", the options for latest:2.X works, but 1.7 etc does not work. Also, please don't just remove old doc, people might be using it.
Contributing to documentation
We welcome documentation contributions!
The text was updated successfully, but these errors were encountered: