Project

General

Custom queries

Profile

Actions

Bug #7718

open

pgsql: fix messages that are skipped (not logged)

Added by Juliana Fajardini Reichow 21 days ago. Updated 10 days ago.

Status:
New
Priority:
Normal
Target version:
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 7.0

Description

Jason shared the pcap attached to this issue, which highlighted that sometimes the pgsql parser
will either not see or at least not log (probably not see) some messages that it should be able to recognize and parse.

From a brief analysis of this capture, I've identified at least two:
- for pgsql.tx_id: 45 there is no request being logged. To understand if it's logged as another transaction, or skipped altogether.
-- related to the above: 54 Simple query requests are sent. Check how many we log.
- there are 5 NoticeResponse messages in that capture. None are logged. I'll create a separate issue to track this.
- the one existing NotificationResponse is also skipped

To investigate and see what more is missed.


Files

TLPW-from-guided-AI-script-pgstress.pcap (28.7 KB) TLPW-from-guided-AI-script-pgstress.pcap Juliana Fajardini Reichow, 05/23/2025 03:36 PM

Subtasks 2 (2 open0 closed)

Bug #7719: pgsql: fix not parsing of NoticeResponse messageNewJuliana Fajardini ReichowActions
Bug #7720: pgsql: fix not parsing of NotificationResponse msgNewJuliana Fajardini ReichowActions
Actions #1

Updated by Juliana Fajardini Reichow 21 days ago

  • Subtask #7719 added
Actions #2

Updated by Juliana Fajardini Reichow 21 days ago

  • Subtask #7720 added
Actions #3

Updated by Juliana Fajardini Reichow 21 days ago

  • Description updated (diff)
Actions #4

Updated by Juliana Fajardini Reichow 21 days ago

  • Description updated (diff)
Actions #5

Updated by Victor Julien 10 days ago

  • Target version changed from 8.0.0 to 8.0.1
Actions

Also available in: Atom PDF