From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Nick Babadzhanian <nb(at)cobra(dot)ru>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pglogical cascading replication (chaining replication) |
Date: | 2016-07-13 16:16:30 |
Message-ID: | 5786695E.2080802@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 07/12/2016 07:20 AM, Nick Babadzhanian wrote:
> I apologize if this is wrong place to ask the question.
>
> A quote from pglogical FAQ:
>
>> Q. Does pglogical support cascaded replication?
>> Subscribers can be configured as publishers as well thus cascaded replication can be achieved
>> by forwarding/chaining (again no failover though).
>
> The only mentions of forwarding on documentation page are:
>
>> Cascading replication is implemented in the form of changeset forwarding.
>
>> forward_origins - array of origin names to forward, currently only supported values are empty
>> array meaning don't forward any changes that didn't originate on provider node, or "{all}"
>> which means replicate all changes no matter what is their origin, default is "{all}"
>
> So my question is how to forward changeset using pglogical?
That's a great question. I have tried to figure out that information as
well. Unfortunately it appears that it is locked up in 2ndQuadrant's
head. I suggest contacting them.
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
From | Date | Subject | |
---|---|---|---|
Next Message | weitzer | 2016-07-13 20:39:24 | Database Architect - Voleon Capital Management LP |
Previous Message | Nick Babadzhanian | 2016-07-13 16:08:53 | Re: pglogical cascading replication (chaining replication) |