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.

Sign up for GitHub

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

Jump to bottom

conn: how to handle invalidated connections #11

Open
dotnwat opened this issue Jan 10, 2017 · 0 comments
Open

conn: how to handle invalidated connections #11

dotnwat opened this issue Jan 10, 2017 · 0 comments

Comments

@dotnwat
Copy link
Member

dotnwat commented Jan 10, 2017

we cache connections based on the log name, but presumably someone could issue a query to force the cache and the log table to not be in sync. this would only happen by explicitly re-configuring the metadata without restarting backends, but it would be nice to be able to handle it some how.
@dotnwat dotnwat changed the title conn: how to handle cached data invalidation conn: how to handle invalidated connections Jan 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dotnwat