Re: libpq: Don't read past the end of a message when tracing it

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Ana Bobillo <anabobillo3(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Subject: Re: libpq: Don't read past the end of a message when tracing it
Date: 2026-11-08 17:23:50
Message-ID: CAN4CZFN_AT9eN6==nUp7kmO8Cm+qnpXnd0wfcmqbaua705+pJg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello

I also noticed this issue, and was planning to investigate it further
later, but I didn't get there yet. I had a bunch of LLM-written test
cases and fuzzing scripts that showcased the issue, and I now
confirmed that all of them are fixed with your patches.

I'll also do a proper review of the patches next week, for now I just
quickly looked at it to confirm that it fixes all of the issues I was
aware of.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-11-08 17:31:56 Re: Draft back-branch release notes are up
Previous Message Sho Ito 2026-11-08 17:15:03 Re: psql: Don't offer partitioned tables after CREATE INDEX CONCURRENTLY