Skip to content

/ timescaledb

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

Jump to bottom

circular warning while backup using pg_dump with version 1.5.1 #1581

Open
comicfans opened this issue Dec 12, 2019 · 5 comments
Open

circular warning while backup using pg_dump with version 1.5.1 #1581

comicfans opened this issue Dec 12, 2019 · 5 comments
Labels
cleanup documentation

Comments

@comicfans
Copy link

@comicfans comicfans commented Dec 12, 2019

Relevant system information:

  • OS: archlinux 64bit kernel 5.1.15
  • PostgreSQL version (output of postgres --version): postgres (PostgreSQL) 11.2
  • TimescaleDB version (output of \dx in psql): 1.5.1
  • Installation method: compile from source

Describe the bug

before upgrade, I'm using timescaledb 1.3, pg_dump gives no warning

pg_dump -U myname --format=custom -f pg_dmp.bak my_db_name

after upgrading to 1.5.1 (and I've also compressed some chunks), same backup commands shows warnings

pg_dump: NOTICE: 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: NOTICE: 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.

I wonder if this is expected behavior , or did I miss-configure something ?
@comicfans comicfans changed the title circle warning while backup using pg_dump with version 1.5.1 circular warning while backup using pg_dump with version 1.5.1 Dec 12, 2019
@Kobus-Smit
Copy link

@Kobus-Smit Kobus-Smit commented Dec 17, 2019

I've got exactly the same warning today while trying compression on my local db.
I'd like to use compression on our prod db (v11.5 (Ubuntu 11.5-1.pgdg18.04+1)) but prefer to wait for feedback first.

Relevant system information:

OS: Windows 10.0.18363.535
PostgreSQL version (output of postgres --version): postgres (PostgreSQL) 11.6
TimescaleDB version (output of \dx in psql): 1.5.1
Installation method: https://docs.timescale.com/latest/getting-started/installation/windows/installation-windows
@bboule bboule added bug and removed investigate question labels Dec 19, 2019
@cevian
Copy link
Contributor

@cevian cevian commented Dec 19, 2019

This warning is expected. It is harmless. We will look at getting rid of it in the future.
@cevian cevian added cleanup documentation and removed bug labels Dec 19, 2019
@MichaHoffmann
Copy link

@MichaHoffmann MichaHoffmann commented Feb 8, 2020

I would be interested in contributing, would this be a good first issue? If so i would need some pointers where to get started!
@mfreed mfreed mentioned this issue Apr 3, 2020
Closed
@AxelTheGerman
Copy link

@AxelTheGerman AxelTheGerman commented May 17, 2020

Glad I found this issue... I don't like scary warnings I don't understand, at least now I know 🙃
@mfreed
Copy link
Member

@mfreed mfreed commented Jun 26, 2020

Additionally, you may receive a WARNING during pg_dump that has caused some conflusion:

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.

This doesn't represent a problem/error, just a little confusing. Just flagging here both if other comes across the issue, but also for the team to get feedback. (cc: @bboule )
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cleanup documentation
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants
@cevian @mfreed @bboule @comicfans @AxelTheGerman @Kobus-Smit @MichaHoffmann
You can’t perform that action at this time.