{"push_id":2582065468,"size":2,"distinct_size":1,"ref":"refs/heads/release-0.29.4","head":"6b06436413760fab77ce85ab1412db6534cbcdb2","before":"69f746432c2dd94cd03770fbd589118bd04211db","commits":[{"sha":"02db33a4be7bca714e742ae51f25d9022dcd5a7b","author":{"name":"Ryan Senior","email":"ea3cd978650417470535f3a4725b6b5042a6ab59@metabase.com"},"message":"Fix memory leak found using RedShift JDBC Metadata methods\n\nRunning sync calls several JDBC metadata methods that return\n`ResultSet` objects. According to the JDBC spec, when the connection\nassociated to the JDBC ResultSet has been closed, it should free the\nresources used by the ResultSets that were left open in that\nconnection. That doesn't look to be happening in RedShift. Closing the\nResutSet instance ourselves before the connection closes will ensure\nthat these resources are freed and doesn't allow the RedShift bug to\noccur.","distinct":false,"url":"https://api.github.com/repos/metabase/metabase/commits/02db33a4be7bca714e742ae51f25d9022dcd5a7b"},{"sha":"6b06436413760fab77ce85ab1412db6534cbcdb2","author":{"name":"Cam Saul","email":"447ad39f04a2b830d871d7e3dd1f696e5835e542@gmail.com"},"message":"Merge pull request #7666 from metabase/fix-redshift-memory-leak\n\nFix memory leak found using RedShift JDBC Metadata methods","distinct":true,"url":"https://api.github.com/repos/metabase/metabase/commits/6b06436413760fab77ce85ab1412db6534cbcdb2"}]}
{"actor":{"display_login":"camsaul"}}