Re: jsonb payload, compression and bandwith usage - Mailing list pgsql-jdbc

From Vladimir Sitnikov
Subject Re: jsonb payload, compression and bandwith usage
Date
Msg-id CAB=Je-GRknNgsNWE2Wp3MCgJrLBGQTYNeFf6R0tLvPCy59Ey5g@mail.gmail.com
Whole thread Raw
In response to Re: jsonb payload, compression and bandwith usage  (Vitalii Tymchyshyn <vit@tym.im>)
List 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


pgsql-jdbc by date:

Previous
From: Vitalii Tymchyshyn
Date:
Subject: Re: jsonb payload, compression and bandwith usage
Next
From: Vladimir Sitnikov
Date:
Subject: Public vs internal APIs