Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Никита Калинин <n(dot)kalinin(at)postgrespro(dot)ru>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Antonin Houska <ah(at)cybertec(dot)at>
Subject: Re: BUG #19500: pgrepack logical decoding plugin can crash assert builds via SQL decoding API
Date: 2026-06-02 12:25:51
Message-ID: ah7HrfedQvqd5zlJ@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Nikita,

On 2026-Jun-02, Никита Калинин wrote:

> > On 2 Jun 2026, at 00:12, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:

> But does the error message need to be that detailed? Perhaps something like
>
> "ERROR: wrong magic number in "pgrepack" decoder plugin"
> would be sufficient.

Maybe. Getting 0x00000000 would be quite different from 0x7f7f7f7f for
instance, or a completely random number, so I don't want to judge ahead
of time.

> Nevertheless, I tested the patch and can confirm that there are no
> assertion failures anymore.
>
> I also ran it under ASAN and did not observe any issues.

Thanks for testing it.

> Would it make sense to add a test for this case from the bug report?

Sure, I would do that.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Saca el libro que tu religión considere como el indicado para encontrar la
oración que traiga paz a tu alma. Luego rebootea el computador
y ve si funciona" (Carlos Duclós)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2026-06-02 18:36:47 BUG #19505: Some weird spikes postgresql processes in database (up to 200k sometime) without apparent reasons.
Previous Message PG Bug reporting form 2026-06-02 08:58:26 BUG #19504: Segmentation fault in plpython3u function (pg19)