RE: WAL archive (archive_mode = always) ?

From: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
To: 'Adelino Silva' <adelino(dot)j(dot)silva(at)googlemail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: WAL archive (archive_mode = always) ?
Date: 2018-10-22 00:47:24
Message-ID: 0A3221C70F24FB45833433255569204D1FAE5273@G01JPEXMBYT05
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: Adelino Silva [mailto:adelino(dot)j(dot)silva(at)googlemail(dot)com]
> What is the advantage to use archive_mode = always in a slave server compared
> to archive_mode = on (shared WAL archive) ?
>
> I only see duplication of Wal files, what is the purpose of this feature ?

This also saves you the network bandwidth by not sending the WAL archive from the primary to the standby(s). The network bandwidth can be costly between remote regions for disaster recovery.

Regards
Takayuki Tsunakawa

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-10-22 00:56:32 Re: More issues with pg_verify_checksums and checksum verification in base backups
Previous Message Michael Paquier 2018-10-22 00:39:56 Re: More issues with pg_verify_checksums and checksum verification in base backups