On Fri, Oct 2, 2009 at 12:26, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I seem to remember that that was discussed and the conclusion was that
> it was reinventing the wheel --- you could perfectly well use ssl/ssh
> compression if you needed it, and you'd want encryption too anyway
> in most plausible scenarios where compression makes sense. (If the
> network trip is long enough to justify compression, it's likely not
> all secure.)
VPN?
In any case: Is setting ssl=true alone enough to ensure that
compression is used? Is there a simple way to test whether or not
compression is used?