How to safely stop replication? #32

New issue

Open

opened 2019-09-10 08:37:28 +00:00 by maiabdelqader · 2 comments

maiabdelqader commented

2019-09-10 08:37:28 +00:00

(Migrated from github.com)

Is there a way to safely stop pg2ch replication?

I need to run pg2ch for few minutes each hour and then to stop it to avoid keeping connections open on PostgreSQL. Is there a way to do that rather than the kill command?

Is there a way to safely stop pg2ch replication? I need to run pg2ch for few minutes each hour and then to stop it to avoid keeping connections open on PostgreSQL. Is there a way to do that rather than the kill command?

mkabilov commented

2019-09-10 08:53:08 +00:00

(Migrated from github.com)

in the current version that might be possible by killing(sending TERM signal) the pg2ch process.

we're currently working on the new version of pg2ch which will allow pausing replication.

in the current version that might be possible by killing(sending TERM signal) the pg2ch process. we're currently working on the new version of pg2ch which will allow pausing replication.

❤️ 2

maiabdelqader commented

2019-09-10 11:59:02 +00:00

(Migrated from github.com)

Is there an side effect for the killing? And when I re-run the pg2ch will it resume from where it reached before the killing?

When it is expected to launch the new version?

Is there an side effect for the killing? And when I re-run the pg2ch will it resume from where it reached before the killing? When it is expected to launch the new version?

This discussion has been locked. Commenting is limited to contributors.