Re: Potential null pointer dereference in postgres.c

From: Maxim Orlov <orlovmg(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Karina Litskevich <litskevichkarina(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Potential null pointer dereference in postgres.c
Date: 2025-01-10 11:08:51
Message-ID: CACG=ezYaAiSU78052ZNaHkwP_iFmGNcw8LPMvuFz5jw3Fh4woQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I have to admit I was wrong with previous v2 patch. Sorry.
Apparently, the chances of committing this very low, but here is the
correct one.

--
Best regards,
Maxim Orlov.

Attachment Content-Type Size
v3-0001-Use-pstrdup-for-remote_host-and-remote_port-save-.patch application/octet-stream 1.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chiranmoy.Bhattacharya@fujitsu.com 2025-01-10 11:10:03 Re: [PATCH] Hex-coding optimizations using SVE on ARM.
Previous Message Zhijie Hou (Fujitsu) 2025-01-10 11:05:58 RE: Conflict detection for update_deleted in logical replication