Re: [PATCH] snowball: fix potential NULL dereference

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Maksim Korotkov <m(dot)korotkov(at)postgrespro(dot)ru>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] snowball: fix potential NULL dereference
Date: 2025-02-18 16:13:48
Message-ID: 1244881.1739895228@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Maksim Korotkov <m(dot)korotkov(at)postgrespro(dot)ru> 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/snowball/README on HEAD, and then extract just
the null-dereference fix to apply to our back branches.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-02-18 16:21:14 Re: Improve cleaning files on Postgres crashes
Previous Message Fujii Masao 2025-02-18 16:08:45 Re: Add “FOR UPDATE NOWAIT” lock details to the log.