Re: Missing NULL check after calling ecpg_strdup

From: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Evgeniy Gorbanev <gorbanyoves(at)basealt(dot)ru>
Subject: Re: Missing NULL check after calling ecpg_strdup
Date: 2025-07-14 14:03:44
Message-ID: CAJ7c6TPn+eO4cVH7urFr+G8d5TmMm0svsVQXjhY_C2LuBm8a7g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Alvaro,

> This looks super baroque. Why not simplify a bit instead? Maybe
> something like
>
> [...]

Fair point. Here is the corrected patch.

Attachment Content-Type Size
v4-0001-Add-proper-checks-for-ecpg_strdup-return-value.patch text/x-patch 6.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-07-14 14:13:40 Re: domain check constraint should also consider domain's collation
Previous Message Álvaro Herrera 2025-07-14 14:02:35 Re: speedup COPY TO for partitioned table.