Project

General

Profile

Actions
Copy link

Bug #8886

closed
JF JF

pgsql: use message type for transaction actions

Bug #8886: pgsql: use message type for transaction actions

Added by Juliana Fajardini Reichow about 2 months ago. Updated 18 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Juliana Fajardini Reichow
Target version:
9.0.0-beta1
Affected Versions:
Effort:
Difficulty:
Label:

Description

parse_request and parse_response were using the parser state for transaction bookkeeping.

This ended up affecting the logging of message types that didn't progress the parser's state:
they didn't get added to the responses array, and thus didn't get logged.

Subtasks 1 (0 open — 1 closed)

Bug #9024: pgsql: use message type for transaction actions (8.0.x backport)ClosedJuliana Fajardini ReichowActions

Related issues 1 (1 open — 0 closed)

Related to Suricata - Bug #8905: pgsql: NoticeResponse and NotificationResponse never pushed to txAssignedJuliana Fajardini ReichowActions

JF Updated by Juliana Fajardini Reichow about 2 months ago Actions
Copy link
 #1

  • Related to Bug #8905: pgsql: NoticeResponse and NotificationResponse never pushed to tx added

JF Updated by Juliana Fajardini Reichow about 2 months ago Actions
Copy link
 #2

  • Status changed from In Progress to In Review

As part of a bigger fix, in GL.

JF Updated by Juliana Fajardini Reichow 24 days ago Actions
Copy link
 #3

  • Status changed from In Review to Resolved
  • Label Needs backport to 8.0 added

OT Updated by OISF Ticketbot 24 days ago Actions
Copy link
 #4

  • Subtask #9024 added

OT Updated by OISF Ticketbot 24 days ago Actions
Copy link
 #5

  • Label deleted (Needs backport to 8.0)

JI Updated by Jason Ish 18 days ago Actions
Copy link
 #6

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: PDF Atom