Re: Memory leak fix in psql - Mailing list pgsql-hackers

From Japin Li
Subject Re: Memory leak fix in psql
Date
Msg-id MEYP282MB166974D3883A1A6E25B5FDAEB68E9@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Whole thread Raw
In response to RE: Memory leak fix in psql  ("tanghy.fnst@fujitsu.com" <tanghy.fnst@fujitsu.com>)
Responses Re: Memory leak fix in psql
List pgsql-hackers
On Wed, 20 Jul 2022 at 14:21, tanghy.fnst@fujitsu.com <tanghy.fnst@fujitsu.com> wrote:
> On Wednesday, July 20, 2022 12:52 PM, Michael Paquier <michael@paquier.xyz> wrote:
>> What about the argument of upthread where we could use a goto in
>> functions where there are multiple pattern validation checks?  Per se
>> v4 attached.
>
> Thanks for your kindly remind and modification.
> I checked v4 patch, it looks good but I think there can be some minor improvement.
> So I deleted some redundant braces around "goto error_return; ".
> Also added an error handle section in validateSQLNamePattern.
>
> Kindly to have a check at the attached v5 patch.
>
> Regards,
> Tang

Thanks for updating the patch.  It looks good.  However, it cannot be
applied on 14 stable.  The attached patches are for 10-14.

-- 
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.


Attachment

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Fast COPY FROM based on batch insert
Next
From: Juan José Santamaría Flecha
Date:
Subject: Re: Windows default locale vs initdb