| From: | Eric Jain <eric(dot)jain(at)gmail(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Compression |
| Date: | 2009-10-26 23:45:38 |
| Message-ID: | e48479d40910261645i1bf166bbk999c6d42d298342b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Fri, Oct 2, 2009 at 12:26, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2009-10-27 09:12:31 | Re: How to ensure that SSL is enabled? |
| Previous Message | Eric Jain | 2009-10-26 23:18:43 | Re: How to ensure that SSL is enabled? |