Re: pglogical cascading replication (chaining replication)

I already tried to contact them, but no luck so far.

Although it seems to me that the change-set is actually forwarded, its the decoding that is failing on the receiving host. Check the log output for p2 and p3 in my previous message.

Regards,
Nick.

----- Original Message -----
From: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
To: "Nick Babadzhanian" <nb(at)cobra(dot)ru>, "pgsql-general" <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, July 13, 2016 7:16:30 PM
Subject: Re: [GENERAL] pglogical cascading replication (chaining replication)

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.