Re: [GENERAL] pglogical cascading replication (chaining replication)

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:

Re: [GENERAL] pglogical cascading replication (chaining replication)

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:

Re: [GENERAL] Merging timeseries in postgres

Nevermind, I misunderstood your question. The answer is an outer join and if you want the exact output you provided then you can use the following clause. coalesce(dx, dx1) as date Is there any reason why these are two different tables? I'd consider changing data structure. - Original

Re: [GENERAL] Merging timeseries in postgres

Whats exactly is wrong with the following query? select dx date, nx, nx1 from test t join test1 t1 on t.dx=t1.dx1 ; - Original Message - From: "Tim Smith" To: "pgsql-general"

Re: [GENERAL] pglogical cascading replication (chaining replication)

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

Re: [GENERAL] pglogical cascading replication (chaining replication)

pglogical apply 13294:1876007473 (PID 14180) exited with >exit code 1 >LOG: starting apply for subscription sub_p2_to_p3_insert_only >ERROR: cache lookup failed for replication origin >'pgl_test_node_p1_provider_sub_p1_t06410f8' >LOG: worker process: pglogical apply 13294

Re: [GENERAL] Replication with non-read-only standby.

echal" <marechal.sylva...@gmail.com> To: "Nick Babadzhanian" <n...@cobra.ru> Cc: "pgsql-general" <pgsql-general@postgresql.org> Sent: Wednesday, July 6, 2016 11:00:05 PM Subject: Re: [GENERAL] Replication with non-read-only standby. 2016-06-30 15:15 GMT+02:00

[GENERAL] pglogical cascading replication (chaining replication)

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

[GENERAL] Replication with non-read-only standby.

Setup: 2 PostgreSQL servers are geographically spread. The first one is used for an application that gathers data. It is connected to the second database that is used to process the said data. Connection is not very stable nor is it fast, so using Bidirectional replication is not an option. It