Fix issue #45, pgbadger will now only reports execute statement of the extended proto...

diff --git a/pgbadger b/pgbadger
index f51670dfdde4cad9b343254d973e874f0bec5842..ce0b66f3df808547702f9867182e2cfd6688e1ce 100755 (executable)
--- a/pgbadger
+++ b/pgbadger
@@ -3695,7 +3695,7 @@ sub parse_query
                        $t_action   = $2;
 
                        # Skipping parse and bind logs
-                       return if ($t_action !~ /query|statement|execute|bind/);
+                       return if ($t_action !~ /query|statement|execute/);
                } elsif (!$duration_required && ($prefix_vars{'t_query'} =~ s/(query|statement): //is)) {
                        $t_action = $1;
                } elsif (!$duration_required && ($prefix_vars{'t_query'} =~ s/(prepare|parse|bind|execute|execute from fetch)\s+[^:]+:\s//is))
@@ -3703,7 +3703,7 @@ sub parse_query
                        $t_action = $1;
 
                        # Skipping parse and bind logs
-                       return if ($t_action !~ /query|statement|execute|bind/);
+                       return if ($t_action !~ /query|statement|execute/);
                } elsif ($prefix_vars{'t_loglevel'} eq 'LOG') {
                        if ($prefix_vars{'t_query'} !~
 /incomplete startup packet|connection|receive|unexpected EOF|still waiting for [^\s]+Lock|checkpoint starting:|could not send data to client|parameter .*configuration file|autovacuum launcher|automatic (analyze|vacuum)|detected deadlock while waiting for|database system was shut down/