Using JSON/JSONB type in postgresql is usually due to the use case that the keys (top level included) can not be predefined. this is the major difference between NoSQL/Document and RDBMS.
Why would TOAST have to be used? Can some speciailly structured "raw" files be used
outside current database files? and jsonb column value would be a pointer to that file.
> Bill Moran wrote: > > > As far as a current solution: my solution would be to decompose the > > JSON into an optimized table. I.e.: > > > > CREATE TABLE store1 ( > > id SERIAL PRIMARY KEY, > > data JSONB > > ); > > > > CREATE TABLE store2 ( > > id INT NOT NULL REFERENCES store1(id), > > top_level_key VARCHAR(1024), > > data JSONB, > > PRIMARY KEY(top_level_key, id) > > ); > > Isn't this what ToroDB already does? > https://www.8kdata.com/torodb/
Looks like. I wasn't aware of ToroDB, thanks for the link. -- Bill Moran