Based on comments in include/catalog/genbki.h and the way most PostgreSQL catalogs are defined, variable length catalog fields should be in the end of the definition and hidden. We need to integrate this rule into our distributed system catalogs
Open
- Dominant language
- C
- Stars
- 12.8k
- Forks
- 794
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 31
Description
Based on comments in include/catalog/genbki.h and also the way most of postgresql catalogs are defined, variable length catalog fields should be in the end of the definition and hidden. This is achieved by including these fields with an #ifdef CATALOG_VARLEN. We need to integrate this rule into our distributed system catalogs.
Contributor guide
Research direction
Start by reading the comments in include/catalog/genbki.h, then inspect the distributed system catalog definitions and compare them with the PostgreSQL catalog convention described in the issue. Done means variable-length catalog fields are placed at the end and hidden with CATALOG_VARLEN where applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, postgresql
- Domain
- databases, distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100