| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Euler Taveira *EXTERN*" <euler(at)timbira(dot)com> |
| Cc: | "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: libpq compression |
| Date: | 2012-06-14 08:07:52 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C20800B960@exadv11.host.magwien.gv.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Euler Taveira wrote:
> There was already some discussion about compressing libpq data
[1][2][3].
> Recently, I faced a scenario that would become less problematic if we
have had
> compression support. The scenario is frequent data load (aka COPY)
over
> slow/unstable links. It should be executed in a few hundreds of
PostgreSQL
> servers all over Brazil. Someone could argue that I could use ssh
tunnel to
> solve the problem but (i) it is complex because it involves a
different port
> in the firewall and (ii) it's an opportunity to improve other
scenarios like
> reducing bandwidth consumption during replication or normal operation
over
> slow/unstable links.
Maybe I'm missing something obvious, but shouldn't a regular SSL
connection (sslmode=require) do what you are asking for?
At least from OpenSSL 0.9.8 on, data get compressed by default.
You don't need an extra port in the firewall for that.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2012-06-14 08:38:10 | Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers. |
| Previous Message | Amit Kapila | 2012-06-14 06:59:16 | Re: hint bit i/o reduction |