query_supervisor #145: error detection during processing a query

Previously, when a pending root query was finished and the end query handler was executed by the Postgres backend executor, the query handlers cleared their state and restarted counting limited values. However, when a pending query was canceled (for example, using the stop button in the PGADMIN query tool), the end handler was not called. As a result, the handlers treated all subsequent queries as subqueries of the already canceled root query. This leaded to situation when new queries were not broken when the time limit was exceeded becaue the timer was not re-armed.

Now an error( including breaking a query) is detected by a handler, and then each created handlers are informed about it. Handlers clear their states during handling an error.

src/query_supervisor/endpoints/initialization.cpp

@@ -28,10 +28,10 @@ std::unique_ptr< PsqlTools::QuerySupervisor::QueryHandlers > g_queryHandlers;
 void _PG_init(void) {
   using PsqlTools::QuerySupervisor::PostgresAccessor;
 
-  LOG_INFO( "Loading query_supervisor.so into backend %d...", getpid() );
+  LOG_DEBUG( "Loading query_supervisor.so into backend %d...", getpid() );
 
   BOOST_SCOPE_EXIT(void) {
-    LOG_INFO( "query_supervisor.so loaded into backend %d...", getpid() );
+    LOG_DEBUG( "query_supervisor.so loaded into backend %d...", getpid() );
   } BOOST_SCOPE_EXIT_END
 
   if ( PostgresAccessor::getInstance().getBackend() == std::nullopt ) {
@@ -50,9 +50,9 @@ void _PG_init(void) {
 }
 
 void _PG_fini(void) {
-  LOG_INFO( "Unloading query_supervisor.so from backend %d...", getpid() );
+  LOG_DEBUG( "Unloading query_supervisor.so from backend %d...", getpid() );
   BOOST_SCOPE_EXIT(void) {
-      LOG_INFO( "query_supervisor.so unloaded from backend %d...", getpid() );
+    LOG_DEBUG( "query_supervisor.so unloaded from backend %d...", getpid() );
   } BOOST_SCOPE_EXIT_END
 
   g_queryHandlers.reset();