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

Running PGSync strictly as WAL consumer #556

Open
KylixSerg opened this issue Jul 21, 2024 · 1 comment
Open

Running PGSync strictly as WAL consumer #556

KylixSerg opened this issue Jul 21, 2024 · 1 comment

Comments

@KylixSerg
Copy link

PGSync version: 3.1.0

Postgres version: 15

Elasticsearch/OpenSearch version: 8.14.3

Redis version: 6.2.1

Python version: 3.11

Feature request(consultation):

First off great work here, pgsync for me works well, but for my use case I would prefer to run it in wal replay only, I would like to avoid using Redis and pg events and subsequently the setup of triggers on my tables - reasoning is that I would run pgsync as a cronjob every X minutes therefore the event system is of no use.

Got a working fork, that essentially passes a bunch of flags downstream to skip said stuff, do you see any issues with running pgsync as a strictly WAL consumer, the cronjob will run about say every 20 minutes - my tables does not get large traffic, so I don't risk piling up WAL in that interval.

@toluaina

@toluaina
Copy link
Owner

Try the polling option. This might satisfy your requirements as it runs a single iteration/cycle and might be more suited for cron

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

No branches or pull requests

2 participants