| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | dmitry(at)koterov(dot)ru |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Replication: GZIP compression in WAL sender/receiver processes communication? |
| Date: | 2013-12-10 01:59:45 |
| Message-ID: | CAB7nPqTm+Fc+X05m-BzGPjPL2fuo+J9W+7T_83S56qK-uaaeig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Dec 10, 2013 at 8:13 AM, Dmitry Koterov <dmitry(at)koterov(dot)ru> wrote:
> Hello.
>
> Is there a way to compress the traffic between master and slave during the
> replication?.. The streaming gzip would be quite efficient for that.
>
> (WAL archiving is not too good for this purpose because of high lag. I just
> need to minimize the cross-datacenter traffic keeping the replication lag
> low.)
Not directly AFAIK, but this would be a good argument for the
implementation of hooks in walsender and walreceiver that could allow
to use such customization of the stream sent and received.
Note that there is also a patch pending for 9.4 that would make
possible the compression of full page writes, reducing globally the
amount of WAL produced by server in exchange of some CPU work to
compress and decompress the data.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2013-12-10 02:15:27 | Re: Replication: GZIP compression in WAL sender/receiver processes communication? |
| Previous Message | Michael Paquier | 2013-12-10 01:49:31 | Re: [Postgres-xc-general] "Tuple not found error" during Index creation |