From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Streaming Replication patch for CommitFest 2009-09 |
Date: | 2009-09-15 04:54:10 |
Message-ID: | 3f0b79eb0909142154qaaea56di9e28eeca00bef99@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Tue, Sep 15, 2009 at 1:06 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> One question I have is what is the level of traffic involved between the
> master and the slave. I know numbers of people have found the traffic
> involved in shipping of log files to be a pain, and thus we get things like
> pglesslog.
That is almost the same as the WAL write traffic on the primary. In fact,
the content of WAL files written to the standby are exactly the same as
those on the primary. Currently SR has provided no compression
capability of the traffic. Should we introduce something like
walsender_hook/walreceiver_hook to cooperate with the add-on program
for compression like pglesslog?
If you always use PITR instead of normal recovery, full_page_writes = off
might be another solution.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Itagaki Takahiro | 2009-09-15 05:21:11 | Re: WIP - syslogger infrastructure changes |
Previous Message | Fujii Masao | 2009-09-15 04:24:22 | Re: Streaming Replication patch for CommitFest 2009-09 |