Skip to content

Conversation

molkazhani2001
Copy link
Contributor

@molkazhani2001 molkazhani2001 commented Aug 21, 2025

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.

  • Improved docstrings for individual functions in pg_replication_pipeline.py, using the word to simulate so that it's clear why we have source and destination pipelines separately.
  • README.md adjusted with the table ownership requirement for non superuser roles.
  • init_replication docstring also adjusted with the table ownership requirement for non superuser roles.

Resolves #640

@molkazhani2001 molkazhani2001 requested a review from VioletM August 21, 2025 11:39
@anuunchin anuunchin self-assigned this Sep 30, 2025
@anuunchin anuunchin force-pushed the enh/pg_reaplication_pipeline branch 4 times, most recently from 98552a1 to ff65c86 Compare September 30, 2025 13:40
@anuunchin anuunchin force-pushed the enh/pg_reaplication_pipeline branch from ff65c86 to cce8d1b Compare September 30, 2025 13:44
Copy link
Contributor

@VioletM VioletM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just small comment

Returns:
None
"""
# create destination pipeline
Copy link
Contributor

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?

Copy link
Collaborator

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 🫡

@anuunchin anuunchin force-pushed the enh/pg_reaplication_pipeline branch from 0d7562e to 9f6cbd3 Compare October 1, 2025 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve pg_replication docs
3 participants