| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cascade replication |
| Date: | 2011-07-19 08:58:33 |
| Message-ID: | CA+U5nMJTMcQWvUkSp_W2U1jbyv1YaRudpzD4vGNaOLZyWuFTTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 11, 2011 at 7:28 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> Attached is the updated version which addresses all the issues raised by
> Simon.
Is there any reason why we disallow cascading unless hot standby is enabled?
ISTM we can just alter the postmaster path for walsenders, patch attached.
Some people might be happier if a sync standby were not HS enabled,
yet able to cascade to other standbys for reading.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| allow_cascading_without_hot_standby.v1.patch | application/octet-stream | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yeb Havinga | 2011-07-19 09:28:53 | Re: [v9.1] sepgsql - userspace access vector cache |
| Previous Message | pasman pasmański | 2011-07-19 08:43:43 | Exclude core dumps from project - example patch |