| From: | Euler Taveira <euler(at)timbira(dot)com> |
|---|---|
| To: | Greg Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Marko Kreen <markokr(at)gmail(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Claes Jakobsson <claes(at)versed(dot)se> |
| Subject: | Re: libpq compression |
| Date: | 2012-06-25 20:50:54 |
| Message-ID: | 4FE8CF2E.2060104@timbira.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25-06-2012 14:30, Greg Jaskiewicz wrote:
> Wasn't this more of an issue in de-coupling compression from encryption ?
>
Let me give a try to take some conclusion. If we decide for an independent
compression code instead of an SSL-based one, that is a possibility to be
tested: SSL + SSL-based compression x SSL + our compression code. If the
latter is faster then we could discuss the possibility to disable compression
in our SSL code and put in documentation that it is recommended to enable
compression in SSL connections.
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-06-25 21:05:42 | Re: libpq compression |
| Previous Message | Euler Taveira | 2012-06-25 20:38:40 | Re: libpq compression |