Re: pg_basebackup compression TODO item

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_basebackup compression TODO item
Date: 2016-03-03 17:31:03
Message-ID: CABUevEwpT6nz8=Mj8ykO3cOJDqtYCgvERF6rZqLEsDVA6JSV3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 3, 2016 at 6:23 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:

> Since SSL compression seems to be a busted flush, I would like to see
> pg_basebackup be able to do compression on the server end, not just
> the client end, in order to spare network bandwidth.
>
> Any comments on how hard this would be, or why we don't want it?
>

I think we want it at protocol level rather than pg_basebackup level. If
SSL compression is busted on base backups, it's equally busted on regular
connection and replication streams. People do ask for compression on that
(in particular I've had a lot of requests when it comes to replication),
and our response there has traditionally been "ssl compression"...

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-03-03 17:34:43 Re: pg_basebackup compression TODO item
Previous Message Jeff Janes 2016-03-03 17:23:31 pg_basebackup compression TODO item