| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | adelino(dot)j(dot)silva(at)googlemail(dot)com |
| Cc: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WAL archive (archive_mode = always) ? |
| Date: | 2018-10-23 12:43:40 |
| Message-ID: | CAMkU=1yR2sd4+YzdVYoPBtWXukS7wnbji72VWVAExA_QS3iYmA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 22, 2018 at 5:06 AM Adelino Silva <
adelino(dot)j(dot)silva(at)googlemail(dot)com> wrote:
> Hello Takayuki,
>
> Sorry can you explain how we can same network bandwidth by not sending the
> WAL archive from the primary to the standby(s).
> I possible scenario is have to multiple standby servers in same host for
> same master. or other scenarios exists ?
>
Before archive_mode = always became available, we've had to stream the WAL
twice, once to the hot standby for immediate application, and once to
pg_receivexlog for archival purposes. So it doubled the bandwidth usage.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2018-10-23 12:50:18 | Re: [HACKERS] proposal: schema variables |
| Previous Message | Tom Lane | 2018-10-23 12:21:31 | Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT |