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/ -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
