Date: Tue, 4 May 2021 10:48:51 +0700
From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: timescaledb backup, pg_dump warnings
Message-ID: <YJDEI9ZRQfAfxdyK@admin.sibptus.ru>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="AM4PZEPayxcaCsBD"
Content-Disposition: inline
Archived-At: 
 <https://www.postgresql.org/message-id/YJDEI9ZRQfAfxdyK%40admin.sibptus.ru>
Precedence: bulk


--AM4PZEPayxcaCsBD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 t=
he
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 C=
OPY TO of a hypertable will not copy any data.
HINT:  Use "COPY (SELECT * FROM <hypertable>) TO ..." to copy all data in h=
ypertable, 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 C=
OPY TO of a hypertable will not copy any data.
HINT:  Use "COPY (SELECT * FROM <hypertable>) TO ..." to copy all data in h=
ypertable, 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 C=
OPY TO of a hypertable will not copy any data.
HINT:  Use "COPY (SELECT * FROM <hypertable>) TO ..." to copy all data in h=
ypertable, 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 C=
OPY TO of a hypertable will not copy any data.
HINT:  Use "COPY (SELECT * FROM <hypertable>) TO ..." to copy all data in h=
ypertable, 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 C=
OPY TO of a hypertable will not copy any data.
HINT:  Use "COPY (SELECT * FROM <hypertable>) TO ..." to copy all data in h=
ypertable, 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 C=
OPY TO of a hypertable will not copy any data.
HINT:  Use "COPY (SELECT * FROM <hypertable>) TO ..." to copy all data in h=
ypertable, 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 C=
OPY TO of a hypertable will not copy any data.
HINT:  Use "COPY (SELECT * FROM <hypertable>) TO ..." to copy all data in h=
ypertable, or copy each chunk individually.


--=20
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet

--AM4PZEPayxcaCsBD
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJgkMQjAAoJEA2k8lmbXsY0zwEIAJe7u/70Y3ZItvcdxTE3gMq3
5ZTCV8I5UbSA0+HmaJz0vBPWDXNE6DrZ8ZHT9i9UaluE3tQt/wOE+MEQr9+ZMRmF
sfgI9L+Ai3Cwejzeb6eScuBaK3g6yzh39YtRS3nYv+6BNJoDZnSqHnmVLkCFuOku
IzSkNVqVyDY3+R8yqcrB3c8bXpBbcwzmU3kfUMc8xhSrup1vpMVKvR2Hrco+5acm
WFKmI3Tb/XJjsHrJlDLiawk9/HJCAdzzT553796wjbmLCh7Lfcr3JSLaUyV0jnmG
x65beBMjH4zO8y4wQZ5c6uNn9cuNy6LJbQw8k6Srr6ybiw0J727eC19kPPKpY8A=
=Vsk4
-----END PGP SIGNATURE-----

--AM4PZEPayxcaCsBD--