Remove reference tables from pg_dist_colocation table
- Dominant language
- C
- Stars
- 12.8k
- Forks
- 794
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 31
Description
We added a new UDF to create reference tables with #892. We also use a valid colocation id for reference tables to determine reference tables by quickly checking the shard count on pg_dist_colocation table. Though, the name of pg_dist_colocation becomes a bit misleading because there is no colocation concept for reference tables.
Two options are;
i. Renaming pg_dist_colocation to something like pg_dist_table_configuration or
ii. Finding another way to figure out reference tables
Related to #879
Contributor guide
Research direction
Start by reviewing the reference-table UDF work from #892 and the related discussion in #879. The issue does not name implementation files or tests; determine whether pg_dist_colocation should be renamed or replaced, and consider the work done when reference tables no longer rely on a misleading colocation concept.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, postgresql
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100