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

[Site Improvement] Issue with the page: /timescaledb/latest/how-to-guides/backup-and-restore/pg-dump-and-restore/ #1040

Closed
jfjoly opened this issue Apr 27, 2022 · 0 comments · Fixed by #1041
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@jfjoly
Copy link
Contributor

jfjoly commented Apr 27, 2022

When executing the backup command, users get a message that is confusing whether the hypertables were backed up correctly.

Related issue: timescale/timescaledb#1797

Describe the bug

pg_dump -Fc -f exampledb.bak -U tsdbadmin -h host -p port tsdb 
Password: 
pg_dump: warning: there are circular foreign-key constraints on this table:
pg_dump:   hypertable
pg_dump: You might not be able to restore the dump without using --disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a --data-only dump to avoid this problem.
pg_dump: warning: there are circular foreign-key constraints on this table:
pg_dump:   chunk
pg_dump: You might not be able to restore the dump without using --disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a --data-only dump to avoid this problem.
pg_dump: NOTICE:  hypertable data are in the chunks, no data will be copied
DETAIL:  Data for hypertables are stored in the chunks of a hypertable so COPY TO of a hypertable will not copy any data.
HINT:  Use "COPY (SELECT * FROM <hypertable>) TO ..." to copy all data in hypertable, or copy each chunk individually.

What do the docs say now?

There is no information about this in the docs now.

What should the docs say?

The documentation should have a mention of this message so that the user understands it's not something to worry about.

Page affected

[Provide the URL to the page you noticed the bug on]

Version affected

Latest

Subject matter expert (SME)

N/A

Screenshots

N/A

@jfjoly jfjoly added documentation Improvements or additions to documentation enhancement New feature or request labels Apr 27, 2022
@charislam charislam self-assigned this Apr 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants