Drop datanode/coordinator connections while handling transaction aborts,
authorPavan Deolasee <[email protected]>
Tue, 15 Dec 2015 11:31:44 +0000 (17:01 +0530)
committerPavan Deolasee <[email protected]>
Tue, 15 Dec 2015 11:31:44 +0000 (17:01 +0530)
overriding persistent_datanode_connections setting

src/backend/pgxc/pool/execRemote.c

index d9c89622a1df975e7ef66b63fd65b87014a570f7..31266eba1b0ae4ac347c1420cacccdb086953ac0 100644 (file)
@@ -3884,7 +3884,15 @@ PreAbort_Remote(void)
 
        pgxc_node_remote_abort();
 
-       if (!temp_object_included && !PersistentConnections)
+       /*
+        * Drop the connections to ensure aborts are handled properly.
+        *
+        * XXX We should really be consulting PersistentConnections parameter and
+        * keep the connections if its set. But as a short term measure, to address
+        * certain issues for aborted transactions, we drop the connections.
+        * Revisit and fix the issue
+        */
+       if (!temp_object_included)
        {
                /* Clean up remote sessions */
                pgxc_node_remote_cleanup_all();