From 41ebbdf499fa367cf0ca5fe09e2cee46104ce35d Mon Sep 17 00:00:00 2001 From: Juliana Fajardini Date: Mon, 17 Aug 2026 11:38:23 -0300 Subject: [PATCH] pgsql: add missing ErrorResponse fields to schema Due to a lack of tests with varied ErrorResponse messages, it wasn't noticed before that these were missing. Partially covers Ticket: #8903 Related to Bug: #8886 --- etc/schema.json | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/etc/schema.json b/etc/schema.json index a96dc8ddc5..52002507a4 100644 --- a/etc/schema.json +++ b/etc/schema.json @@ -5068,7 +5068,8 @@ "Indicates if a password message was received but not logged due to Suricata settings" }, "process_id": { - "type": "integer" + "type": "integer", + "description": "The process id of the target backend, as seen in CancelRequests messages" }, "protocol_version": { "type": "string" @@ -5207,7 +5208,8 @@ "type": "string" }, "message": { - "type": "string" + "type": "string", + "description": "The PostgreSQL message type seen on the wire. Or the primary human-readable error/notice PostgreSQL message present in an ErrorResponse message" }, "parameter_status": { "type": "array", @@ -5252,8 +5254,13 @@ } } }, + "position": { + "type": "string", + "description": "String, representing a decimal ASCII integer, related to an error cursor position as an index to original PostgreSQL query string, as seen in an ErrorResponse message" + }, "process_id": { - "type": "integer" + "type": "integer", + "description": "The process id of the backend process, as seen in BackendKeyData messages" }, "routine": { "type": "string" @@ -5269,6 +5276,10 @@ }, "ssl_accepted": { "type": "boolean" + }, + "where": { + "type": "string", + "description": "'where' field in an ErrorResponse PostgreSQL message, indicating the context in which the error occurred" } } },