-
Notifications
You must be signed in to change notification settings - Fork 70
add a typical example of initial load #648
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
98552a1
to
ff65c86
Compare
ff65c86
to
cce8d1b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just small comment
sources/pg_replication_pipeline.py
Outdated
Returns: | ||
None | ||
""" | ||
# create destination pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's not call it the destination pipeline! Pipeline is a connection between source and destination, can we just call it replication_pipeline
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how about we call them simulation and replication pipelines - i finally understand from the user perspective how source and destination pipelines
sounds odd 🫡
0d7562e
to
9f6cbd3
Compare
This PR adds an example to
the pg_replication_pipeline.py
that does NOT simulate a source postgres, so that users have a better idea on how to use pg_replication in production scenarios.pg_replication_pipeline.py
, using the wordto simulate
so that it's clear why we have source and destination pipelines separately.init_replication
docstring also adjusted with the table ownership requirement for non superuser roles.Resolves #640