Re: Wire protocol compression - Mailing list pgsql-hackers

From Shulgin, Oleksandr
Subject Re: Wire protocol compression
Date
Msg-id CACACo5QabX=RRT8-wdq7+Mbx+zEc6bEmY8UReBAc=eGtLUGhfQ@mail.gmail.com
Whole thread Raw
In response to Re: Wire protocol compression  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
Responses Re: Wire protocol compression  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
List pgsql-hackers
On Thu, Apr 21, 2016 at 11:07 AM, Aleksander Alekseev <a.alekseev@postgrespro.ru> wrote:
> Does it make sense to you guys to discuss compression outside of TLS?
> There are potentially huge bandwidth savings which could benefit both
> WAN and non-WAN scenarios, and decoupling this problem from TLS would
> make it both accessible to everyone (assuming PostgreSQL clients
> follow). It would be a protocol change though.

I personally don't think it's something that should be implemented in
PostgreSQL core. As a third-party TCP-proxy (on both client and server
sides) with gzip/lz4 support perhaps. I'll be not surprised if it turns
out that such projects already exist.


I guess since the usual answer for compression was "use what SSL provides you for free", it's rather unlikely that someone bothered to make a proxy just for that purpose, and really, a proxy is just another moving part in your setup: not everyone will be thrilled to add that.

--
Alex

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Timeline following for logical slots
Next
From: Michael Paquier
Date:
Subject: Re: Optimization for updating foreign tables in Postgres FDW