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

Support reads from replicas #9

Open
jesperpedersen opened this issue Aug 28, 2019 · 4 comments
Open

Support reads from replicas #9

jesperpedersen opened this issue Aug 28, 2019 · 4 comments
Labels
feature New feature

Comments

@jesperpedersen
Copy link
Collaborator

This should be done as a separate pipeline

@jesperpedersen jesperpedersen added the feature New feature label Aug 28, 2019
@dtseiler
Copy link

Do you mean routing SELECTs to replicas here, while keeping DML on a primary?

What if I just want to set up an entry for a replica DB? I'm not interested (yet) in fancy statement routing. I just want to have an entry that points to my primary and a separate entry that points to my replica. I'll have my app determine which connection to use. Can pgagroal support that today?

@digoal
Copy link

digoal commented May 28, 2020

how to filter udf, when select udf, which udf has some dml or nested udf has some dml.

@jesperpedersen
Copy link
Collaborator Author

jesperpedersen commented May 28, 2020

@dtseiler pgagroal will allow connections to replicas at the moment. However, it does not check any of the messages sent, so you may get errors if you are doing INSERT, UPDATE, DELETE, UDF, ...

@digoal Precisely, this is a big concern about this feature.

Since it is an active issue it will be on the roadmap at some point, but I can't say when it will hit a release.

@dtseiler
Copy link

Right so you were originally talking about statement routing. That wasn't obvious to me from the title of the issue. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

3 participants