From: | Álvaro Hernández Tortosa <aht(at)8kdata(dot)com> |
---|---|
To: | Bill Moran <wmoran(at)potentialtech(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Tom Smith <tomsmith1989sk(at)gmail(dot)com>, Thomas Kellerer <spam_eater(at)gmx(dot)net>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: JSONB performance enhancement for 9.6 |
Date: | 2016-02-09 04:38:31 |
Message-ID: | 56B96D47.4080001@8kdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 20/01/16 13:32, Bill Moran wrote:
> On Tue, 19 Jan 2016 23:53:19 -0300
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>
>> 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.
>
Hi Bill.
Effectively, that's what ToroDB does. You will have a dynamic
schema, but automatically created for you. It will be a relational
schema, no json/jsonb needed for your data.
Please read the FAQ: https://github.com/torodb/torodb/wiki/FAQ and
let us know (https://groups.google.com/forum/#!forum/torodb-dev) if you
would have any additional question.
Thanks, Álvaro, for the reference :)
Cheers,
Álvaro
From | Date | Subject | |
---|---|---|---|
Next Message | subhan alimy | 2016-02-09 06:57:40 | Postgresql Server Upgarde |
Previous Message | Tom Smith | 2016-02-09 04:10:54 | Re: JSONB performance enhancement for 9.6 |