Re: jsonb payload, compression and bandwith usage

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Vitalii Tymchyshyn <vit(at)tym(dot)im>
Cc: Dave Cramer <pg(at)fastcrypt(dot)com>, Yann Le Moigne <ylemoigne(at)javatic(dot)fr>, List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: jsonb payload, compression and bandwith usage
Date: 2015-07-23 15:21:21
Message-ID: CAB=Je-GRknNgsNWE2Wp3MCgJrLBGQTYNeFf6R0tLvPCy59Ey5g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

> How about SSL?

I think it was discussed here:
http://www.postgresql.org/message-id/CAMsr+YFh1J72bckTZe0te+eJCJ=JnW-g-q_KQhFg_thVdxKxDw@mail.gmail.com

TLDR: "real answer is probably to just add PostgreSQL protocol-level
support for compression, rather than trying to (ab)use SSL for it."

Another option is SSH port forwarding (SSH can do transparent compression).

Vladimir

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Vladimir Sitnikov 2015-07-23 15:32:54 Public vs internal APIs
Previous Message Vitalii Tymchyshyn 2015-07-23 15:09:14 Re: jsonb payload, compression and bandwith usage