The solution was found thanks to Petr Jelinek from 2ndQ.
> Cascading wasn't much of a priority so far.
> Currently you have to create the origin manually using
> pg_replication_origin_create().
> I plan to make this work seamlessly in the future release.
So whats needed to be done is:
on p2:
The solution was found thanks to Petr Jelinek from 2ndQ.
> Cascading wasn't much of a priority so far.
> Currently you have to create the origin manually using
> pg_replication_origin_create().
> I plan to make this work seamlessly in the future release.
So whats needed to be done is:
on p1:
oshua D. Drake" <j...@commandprompt.com>
To: "Nick Babadzhanian" <n...@cobra.ru>, "pgsql-general"
<pgsql-general@postgresql.org>
Sent: Wednesday, July 13, 2016 7:16:30 PM
Subject: Re: [GENERAL] pglogical cascading replication (chaining replication)
On 0
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
After checking logs I noticed this error on p3-node:
>ERROR: cache lookup failed for replication origin
>'pgl_test_node_p1_provider_sub_p1_t06410f8'
pgl_test_node_p1_provider_sub_p1_t06410f8 is origin for p1-node.
Here are the logs from all three server (this happens every time I insert
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
