| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | adelino(dot)j(dot)silva(at)googlemail(dot)com |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WAL archive (archive_mode = always) ? |
| Date: | 2018-10-19 23:59:37 |
| Message-ID: | CAMkU=1zv6ihzih5vFwq0Xu_Ts-9hg923pZS45EhDG03=VcteXA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 19, 2018 at 10:00 AM Adelino Silva <
adelino(dot)j(dot)silva(at)googlemail(dot)com> wrote:
> Hi,
>
> 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 ?
>
You might not have a shared wal archive in the first place. For example,
your only access to the master is through the streaming replication
protocol, but you want to maintain a local WAL archive anyway so you can
PITR locally for testing or debugging purposes.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2018-10-20 01:07:02 | Re: Code of Conduct plan,Re: Code of Conduct plan |
| Previous Message | Dmitry Molotkov | 2018-10-19 23:58:21 | Re: BUG #15446: Crash on ALTER TABLE |