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