From: | Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com> |
---|---|
To: | Dorian Hoxha <dorian(dot)hoxha(at)gmail(dot)com> |
Cc: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ZSON, PostgreSQL extension for compressing JSONB |
Date: | 2016-10-05 06:09:48 |
Message-ID: | CAKOSWNkmw-xOK7X2+psSncf__93dUm2L3E5ZycZTyHra1LMGXg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/4/16, Dorian Hoxha <dorian(dot)hoxha(at)gmail(dot)com> wrote:
> On Tue, Oct 4, 2016 at 5:34 PM, Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> wrote:
>> Hello, Simon.
>>
>> Thanks for you interest to this project!
>>
>> > Will you be submitting this to core?
>>
>> 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?
>
> ~everyone wants lower data storage and wants some kind of compression.
> Can this be made to automatically retrain when analyzing (makes sense?)?
> And create a new dictionary only if it changes compared to the last one.
ANALYZE does not walk through all the table and does not change its records.
Creating a new dictionary for compressing purposes supposes updating
rows of the original table to replace entries to references to a
dictionary.
--
Best regards,
Vitaly Burovoy
From | Date | Subject | |
---|---|---|---|
Next Message | PHANIKUMAR G | 2016-10-05 10:34:21 | Re: postgres failed to start from services manager on windows 2008 r2 |
Previous Message | Tatsuo Ishii | 2016-10-05 04:34:09 | PGConf.Asia and visa |