From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Israel Ben Guilherme Fonseca" <israel(dot)bgf(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Incoming/Sent traffic data |
Date: | 2011-05-13 17:17:10 |
Message-ID: | 1008.1305307030@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Israel Ben Guilherme Fonseca <israel(dot)bgf(at)gmail(dot)com> wrote:
>> But here is the question, does the SSL compress the data too?
> It can, if that is negotiated properly:
> http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#comp
> Apparently the JDBC driver isn't attempting to negotiate
> compression. I don't know how hard that would be to change.
What surprises me here is not so much that JDBC doesn't enable SSL
compression as that the python case does. I remember people complaining
that libpq doesn't enable SSL compression, which is unsurprising given
what it says on that FAQ page. Is the python test not using a
libpq-based client library?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Maciek Sakrejda | 2011-05-13 17:18:12 | Re: Incoming/Sent traffic data |
Previous Message | Israel Ben Guilherme Fonseca | 2011-05-13 17:12:54 | Re: Incoming/Sent traffic data |