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
As I understand, the current way to deal with long running queries is to close the respective db connections (and create new ones to still maintain the configured pool size).
* occ configurations logging
* cal event success
* adding cal data
* added TODOs
* Remove log_occ_confogs.go
* Remove testing files
* source of configs - files
* whitelist format change
* code clean up
* code review changes-1
* CR fixes
* CR fixes
* Delete tests/unittest/config_logging/main_test.go
* clean up
* Merge branch 'occ-config-logging' of /Users/simmidisetty/Documents/GitHub/OpenSourceHera/src/github.com/paypal/hera with conflicts.
* test for config logging
* removing test changes
* tests for all cases
* test
* making minor changes for logging feature specific data
* changes for incorporate review comments
---------
Co-authored-by: satyakamala03 <128077872+satyakamala03@users.noreply.github.com>
Co-authored-by: simmidisetty <simmidisetty@paypal.com>
Co-authored-by: Rajesh S <samal.rajesh@gmail.com>
As I understand, the current way to deal with long running queries is to close the respective db connections (and create new ones to still maintain the configured pool size).
It should be more performant to send explicit cancel requests to the db. Some more info in the link below.
https://asktom.oracle.com/m/pls/asktom/asktom.search?tag=cancelling-long-running-queries
The text was updated successfully, but these errors were encountered: