pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedtimescaledb backup, pg_dump warnings
3+ messages / 3 participants
[nested] [flat]
* timescaledb backup, pg_dump warnings
@ 2021-05-04 03:48 Victor Sudakov <vas@sibptus.ru>
0 siblings, 1 reply; 3+ messages in thread
From: Victor Sudakov @ 2021-05-04 03:48 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Dear Colleagues,
Is anyone using the Timescaledb extension? I've read
https://docs.timescale.com/latest/using-timescaledb/backup, it says that
restoring data from a backup currently requires some additional
procedures. I'm fine with that.
However, the actual pg_dump produces multiple warnings, do they mean that the
timescaledb database is corrupt, or the dump will come out corrupt?
Below is a sample of the warnings (Postgres 12.6, Timescaledb 2.2.0):
$ pg_dump -Fc -U postgres -f zabbix.dump -d zabbix
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.
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.
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.
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.
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.
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.
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.
--
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet
Attachments:
signature.asc (application/pgp-signature, 454B) download
^ permalink raw reply [nested|flat] 3+ messages in thread
* RE: [EXTERNAL] timescaledb backup, pg_dump warnings
@ 2021-05-06 13:20 Godfrin, Philippe E <philippe.godfrin@nov.com>
parent: Victor Sudakov <vas@sibptus.ru>
0 siblings, 1 reply; 3+ messages in thread
From: Godfrin, Philippe E @ 2021-05-06 13:20 UTC (permalink / raw)
To: vas@sibptus.ru; pgsql-admin@lists.postgresql.org
HI – the messages that say “pg_dump: NOTICE: hypertable data are in the chunks, no data will be copied" are noise. My understanding is that is messaging that is no longer applicable, but test it for certain. You could check here: https://github.com/timescale/timescaledb
The circular constraints has been an issue since December 2019 https://github.com/timescale/timescaledb/issues/1581. I don’t have a resolution, except to follow the instructions and test.
Regards,
Phil godfrin
From: Victor Sudakov <vas@sibptus.ru>
Sent: Monday, May 3, 2021 10:49 PM
To: pgsql-admin@lists.postgresql.org
Subject: [EXTERNAL] timescaledb backup, pg_dump warnings
Use caution when interacting with this [EXTERNAL] email!
Dear Colleagues,
Is anyone using the Timescaledb extension? I've read
https://docs.timescale.com/latest/using-timescaledb/backup, it says that
restoring data from a backup currently requires some additional
procedures. I'm fine with that.
However, the actual pg_dump produces multiple warnings, do they mean that the
timescaledb database is corrupt, or the dump will come out corrupt?
Below is a sample of the warnings (Postgres 12.6, Timescaledb 2.2.0):
$ pg_dump -Fc -U postgres -f zabbix.dump -d zabbix
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.
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.
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.
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.
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.
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.
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.
--
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [EXTERNAL] timescaledb backup, pg_dump warnings
@ 2021-05-07 00:39 Piyaphart Samutkang <piyaphat.orp@gmail.com>
parent: Godfrin, Philippe E <philippe.godfrin@nov.com>
0 siblings, 0 replies; 3+ messages in thread
From: Piyaphart Samutkang @ 2021-05-07 00:39 UTC (permalink / raw)
To: Godfrin, Philippe E <philippe.godfrin@nov.com>; +Cc: vas@sibptus.ru; pgsql-admin@lists.postgresql.org
ในวันที่ พฤ. 6 พ.ค. 2021 20:21 Godfrin, Philippe E <philippe.godfrin@nov.com>
เขียนว่า:
> HI – the messages that say “pg_dump: NOTICE: hypertable data are in the
> chunks, no data will be copied" are noise. My understanding is that is
> messaging that is no longer applicable, but test it for certain. You could
> check here: https://github.com/timescale/timescaledb
>
>
>
> The circular constraints has been an issue since December 2019
> https://github.com/timescale/timescaledb/issues/1581. I don’t have a
> resolution, except to follow the instructions and test.
>
> Regards,
>
> Phil godfrin
>
>
>
> *From:* Victor Sudakov <vas@sibptus.ru>
> *Sent:* Monday, May 3, 2021 10:49 PM
> *To:* pgsql-admin@lists.postgresql.org
> *Subject:* [EXTERNAL] timescaledb backup, pg_dump warnings
>
>
>
> Use caution when interacting with this [EXTERNAL] email!
>
> Dear Colleagues,
>
> Is anyone using the Timescaledb extension? I've read
> https://docs.timescale.com/latest/using-timescaledb/backup, it says that
> restoring data from a backup currently requires some additional
> procedures. I'm fine with that.
>
> However, the actual pg_dump produces multiple warnings, do they mean that
> the
> timescaledb database is corrupt, or the dump will come out corrupt?
> Below is a sample of the warnings (Postgres 12.6, Timescaledb 2.2.0):
>
> $ pg_dump -Fc -U postgres -f zabbix.dump -d zabbix
> 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.
> 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.
> 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.
> 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.
> 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.
> 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.
> 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.
>
>
>
>
> --
> Victor Sudakov VAS4-RIPE
> http://vas.tomsk.ru/
> 2:5005/49@fidonet
>
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2021-05-07 00:39 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-05-04 03:48 timescaledb backup, pg_dump warnings Victor Sudakov <vas@sibptus.ru>
2021-05-06 13:20 ` Godfrin, Philippe E <philippe.godfrin@nov.com>
2021-05-07 00:39 ` Piyaphart Samutkang <piyaphat.orp@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox