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

Citus treats pg_shard tables as local when missing metadata #11

Closed
jasonmp85 opened this issue Dec 5, 2014 · 2 comments · Fixed by #103
Closed

Citus treats pg_shard tables as local when missing metadata #11

jasonmp85 opened this issue Dec 5, 2014 · 2 comments · Fixed by #103
Assignees
Milestone

Comments

@jasonmp85
Copy link
Collaborator

From @sumedhpathak on November 20, 2014 0:27

If someone doesn't copy over the metadata from pg_shard to CitusDB, but sets use_citusdb_select_logic to true, in CitusDB we treat all pg_shard tables as local tables and read the empty table on the master node, returning 0 results.

This is minor, but can be a usability issue with CitusDB/pg_shard integration.

@jasonmp85 jasonmp85 changed the title Citus erroneously treats table as local when missing metadata Citus treatss pg_shard tables as local when missing metadata Dec 5, 2014
@jasonmp85 jasonmp85 changed the title Citus treatss pg_shard tables as local when missing metadata Citus treats pg_shard tables as local when missing metadata Dec 5, 2014
@jasonmp85 jasonmp85 added this to the v1.1 milestone Dec 9, 2014
@jasonmp85 jasonmp85 modified the milestones: v1.1, v1.2 Feb 24, 2015
@jasonmp85
Copy link
Collaborator Author

Possibly fixed by #27.

@jasonmp85
Copy link
Collaborator Author

Confirming that #103 obviates this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant