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
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.
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
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
The text was updated successfully, but these errors were encountered: