| From: | Vitalii Tymchyshyn <vit(at)tym(dot)im> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com>, Yann Le Moigne <ylemoigne(at)javatic(dot)fr> |
| Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: jsonb payload, compression and bandwith usage |
| Date: | 2015-07-23 15:09:14 |
| Message-ID: | CABWW-d1Pq4Seoz+qFOtsD8cmPVXcHovoUCyk2q_m5Rspu4siXg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
How about SSL? It may be an overkill, but SSL usually has some sort of
compression.
Ср, 22 лип. 2015 14:23 Dave Cramer <pg(at)fastcrypt(dot)com> пише:
> Unfortunately no. The backend would need to understand this, and it doesn't
>
> Dave Cramer
>
> dave.cramer(at)credativ(dot)ca
> http://www.credativ.ca
>
> On 22 July 2015 at 12:45, Yann Le Moigne <ylemoigne(at)javatic(dot)fr> wrote:
>
>> Hi,
>>
>> Currently, I use PgObject to store a document in a jsonb column.
>>
>> But in my usecase ; network bandwith is limited and jsonb as string is
>> quite heavy. (Between 2-5 Mbyte).
>> Something like gzip is very effective to reduce the size of the payload
>> (about 70%).
>>
>> So is there any support for compression in current jdbc driver ?
>> If yes, is it active by default ? (I don’t see any option in driver
>> documentation to enable ou disable it).
>> If no, is there an alternative way to handle it ? (like handling json
>> (de)compression at application level, et create some sort of automatic
>> conversion on postgres side).
>>
>> Thanks for your attention,
>> Best Regards,
>> Yann.
>>
>> --
>> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-jdbc
>>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2015-07-23 15:21:21 | Re: jsonb payload, compression and bandwith usage |
| Previous Message | Dave Cramer | 2015-07-22 17:36:28 | Re: jsonb payload, compression and bandwith usage |