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

New approach to PostgreSQL NOTIFY/LISTEN handling #777

Open
Dennis4b opened this issue Oct 1, 2018 · 0 comments
Open

New approach to PostgreSQL NOTIFY/LISTEN handling #777

Dennis4b opened this issue Oct 1, 2018 · 0 comments

Comments

@Dennis4b
Copy link

Dennis4b commented Oct 1, 2018

(Issue added on request after Gitter question)

With the new 6.0-branch changes (running queries on different ExecutionContexts, cats-effect scheduling and timer changes) there might be a more elegant way to listen for and stream PostgreSQL notifications that do not rely on a burnerthread and Thread.sleep calls.

All suggestions appreciated.

First improvement: replace HC.delay{ Thread.sleep(...) } with timer.sleep(...).to[ConnectionIO] (where timer is a Timer[IO], see cats-effect docs.). More suggestions welcome.

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

1 participant