Re: [PATCH] snowball: fix potential NULL dereference

2025-02-18 Thread Tom Lane
Maksim Korotkov writes: > On 2025-02-11 19:53, Tom Lane wrote: >> You should report this upstream; >> (Whenever they apply the patch, we should then re-sync...) > FYI, the patch to fix this problem was applied by upstream. Thanks. Barring objections, I'll do a full resync per src/backend/snowba

Re: [PATCH] snowball: fix potential NULL dereference

2025-02-18 Thread Maksim Korotkov
Hi On 2025-02-11 19:53, Tom Lane wrote: You should report this upstream; (Whenever they apply the patch, we should then re-sync...) FYI, the patch to fix this problem was applied by upstream. --- Best regards, Korotkov Maksim PostgresPro m.korot...@postgrespro.ru

Re: [PATCH] snowball: fix potential NULL dereference

2025-02-11 Thread Tom Lane
=?utf-8?q?=D0=9A=D0=BE=D1=80=D0=BE=D1=82=D0=BA=D0=BE=D0=B2_=D0=9C=D0=B0=D0=BA=D1=81=D0=B8=D0=BC?= writes: > I found the case of potential NULL pointer dereference. > In snowball/libstemmer/api.c if we transfer control to the SN_create_env() > function > by using the error label when there is a m