-
Notifications
You must be signed in to change notification settings - Fork 106
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 docs for MN migration to TimescaleDB instance #2827
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-mn_migration |
|
||
```bash | ||
pg_restore -U tsdbadmin -W \ | ||
-h <HOST> -p <PORT> --no-owner -Fc \ |
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.
Do you need the -Fc
here? I think pg_restore
figures out this itself and the documentation for pg_dump
and pg_restore
does not use it.
b32a77a
to
2d9956f
Compare
Description
Documentation changes to describe migration from self-hosted Multi-node deployments to TimescaleDB instance using COPY or timescaledb-parallel-copy
Links
Fixes #[insert issue link, if any]
Writing help
For information about style and word usage, see the style guide
Review checklists
Reviewers: use this section to ensure you have checked everything before approving this PR:
Subject matter expert (SME) review checklist
Documentation team review checklist
and have they been implemented?