In #103, we discovered that using low-level operations is kind of unwieldy when the code needs to switch between different backing stores. By using SPI, we can overlay a VIEW on the CitusDB metadata catalogs and have everything "just work".
This change prepares for that by switching to SPI for our metadata functions. The functions will now respect any VIEW or TRIGGER we need to adapt to CitusDB's underlying representation.
In #103, we discovered that using low-level operations is kind of unwieldy when the code needs to switch between different backing stores. By using SPI, we can overlay a
VIEW
on the CitusDB metadata catalogs and have everything "just work".This change prepares for that by switching to SPI for our metadata functions. The functions will now respect any
VIEW
orTRIGGER
we need to adapt to CitusDB's underlying representation.