| From: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: ZSON, PostgreSQL extension for compressing JSONB |
| Date: | 2016-10-05 15:58:37 |
| Message-ID: | 20161005155837.GA31519@e733.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > I could align ZSON to PostgreSQL code style. I only need to run pgindent
> > and write a few comments. Do you think community would be interested in
> > adding it to /contrib/ ? I mean doesn't ZSON solve a bit too specific
> > problem for this?
>
> CREATE COMPRESSION DICTIONARY public.simple_dict (
> WORDS = my_json_schema
> );
>
> Then use the dictionary by referencing the DictionaryId within the
> datatype modifier, e.g. ZSON(357)
>
> That way we can use this for TEXT, XML, JSON etc.. as ZTEXT, ZXML, ZJSON
>
> So it seems like a generally useful thing to me.
Good idea!
What about evolving schema of JSON/JSONB/XML? For instance,
adding/removing keys in new versions of the application. UPDATE
COMPRESSION DICTIONARY?
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darren Lafreniere | 2016-10-05 18:20:06 | BRIN indexes and ORDER BY |
| Previous Message | Simon Riggs | 2016-10-05 15:47:49 | Re: ZSON, PostgreSQL extension for compressing JSONB |