Actions
Bug #7000
closedOptimization #7026: app-protos: trigger raw stream reassembly
pgsql: trigger raw stream reassembly
Affected Versions:
Effort:
Difficulty:
Label:
Description
When a new PgsqlTransaction was created, the tx_id was adjusted to start at 1.
Disconsidering this, get_tx and free_tx were still incrementing tx_id when performing their logics,
leading to discrepancies when logging alert metadata for pgsql (to name one that we were able to notice).
This might also happen with template.rs, will investigate.
---------------
Update: turns out that the template code also takes this into consideration, as well as the core of the engine.
So the solution here was actually to trigger the raw stream reassembly earlier, so, I added this one as a sub ticket of #7026
Updated by Juliana Fajardini Reichow about 1 year ago
- Status changed from In Progress to In Review
Updated by Jason Ish about 1 year ago
- Related to Bug #7004: app-layer: wrong tx may be logged for stream rules added
Updated by Juliana Fajardini Reichow 12 months ago
- Related to Optimization #7018: dns/tcp: allow triggering raw stream reassembly added
Updated by Victor Julien 11 months ago
- Related to Bug #7113: pgsql: track 'progress' in tx per direction added
Updated by Juliana Fajardini Reichow 7 months ago
- Subject changed from pgsql: partially incorrect tx_id tracking to pgsql: trigger raw stream reassembly
Updated by Juliana Fajardini Reichow 7 months ago
- Has duplicate Optimization #7076: pgsql: trigger raw stream reassembly when tx completed added
Actions