From d676d711ee134bf6b88cada82dbab812947d26eb Mon Sep 17 00:00:00 2001
From: Juliana Fajardini <jufajardini@gmail.com>
Date: Mon, 17 Feb 2025 12:06:39 -0300
Subject: [PATCH] pgsql: add case for Unknown response message state

No state change, but since we added Unknown responses, we should handle
that case -- should we have a specific state for such cases?

Related to
Bug #5524
Task #5566
---
 rust/src/pgsql/pgsql.rs | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/rust/src/pgsql/pgsql.rs b/rust/src/pgsql/pgsql.rs
index 513e24cf7e..b1b8f87c69 100644
--- a/rust/src/pgsql/pgsql.rs
+++ b/rust/src/pgsql/pgsql.rs
@@ -291,7 +291,7 @@ impl PgsqlState {
                 Some(PgsqlStateProgress::ConnectionTerminated)
             }
             PgsqlFEMessage::UnknownMessageType(_) => {
-                SCLogDebug!("Match: Unknown message type");
+                SCLogDebug!("Match: Unknown request message type");
                 // Not changing state when we don't know the message
                 None
             }
@@ -496,6 +496,11 @@ impl PgsqlState {
                 // query was sent with what we received here?
                 Some(PgsqlStateProgress::CommandCompletedReceived)
             }
+            PgsqlBEMessage::UnknownMessageType(_) => {
+                SCLogDebug!("Match: Unknown response message type");
+                // Not changing state when we don't know the message
+                None
+            }
             PgsqlBEMessage::ErrorResponse(_) => Some(PgsqlStateProgress::ErrorMessageReceived),
             _ => {
                 // We don't always have to change current state when we see a response...