You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
dotnwat
changed the title
conn: how to handle cached data invalidation
conn: how to handle invalidated connections
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.
The text was updated successfully, but these errors were encountered: