> 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