| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | hlinnaka <hlinnaka(at)iki(dot)fi> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Venkata Balaji N <nag1010(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Borodin Vladimir <root(at)simply(dot)name>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Streaming replication and WAL archive interactions |
| Date: | 2015-04-22 18:30:48 |
| Message-ID: | CA+Tgmoa_Fwi+q4EKu+SYszowBN5k5LYDY4VkFOtmzkez2PdYLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 22, 2015 at 2:17 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> Note that it's a bit complicated to set up that scenario today. Archiving is
> never enabled in recovery mode, so you'll need to use a custom cron job or
> something to maintain the archive that C uses. The files will not
> automatically flow from B to the second archive. With the patch we're
> discussing, however, it would be easy: just set archive_mode='always' in B.
Hmm, I see. But if C never replays the last, partial segment from the
old timeline, how does it follow the timeline switch?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Payal Singh | 2015-04-22 18:48:49 | Re: Add CINE for ALTER TABLE ... ADD COLUMN |
| Previous Message | Robert Haas | 2015-04-22 18:27:37 | Re: Freeze avoidance of very large table. |