Skip to content
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

feat: Custom replication slot name #540

Open
edgarrmondragon opened this issue Nov 12, 2024 · 0 comments
Open

feat: Custom replication slot name #540

edgarrmondragon opened this issue Nov 12, 2024 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers python Pull requests that update Python code

Comments

@edgarrmondragon
Copy link
Member

Hi everyone. I'm using tap-postgres with LOG_BASED replication method. I've successfully setup the logical replication and now able to capture insert, update, and deletes on my database.

I'm running into an issue that my replication slot cannot be used by parallel extractions from the database. Is there a way to set a different replication slot name for each extractor other than tappostgres?

This should be as easy as adding new setting to tap_postgres/tap.py and passing it to

logical_replication_cursor.start_replication(
slot_name="tappostgres",
decode=True,
start_lsn=start_lsn,
status_interval=status_interval,
options={
"format-version": 2,
"include-transaction": False,
"add-tables": self.fully_qualified_name,
},
)

Slack Thread: https://meltano.slack.com/archives/C069CQNHDNF/p1731396392068079

@edgarrmondragon edgarrmondragon added enhancement New feature or request good first issue Good for newcomers python Pull requests that update Python code labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers python Pull requests that update Python code
Projects
Development

No branches or pull requests

1 participant