From: | Zhihong Yu <zyu(at)yugabyte(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: free C string |
Date: | 2021-07-14 18:29:23 |
Message-ID: | CALNJ-vSJJksKkrmpS-yCWt4rj5xfT+S5j40y13oFqGn3wZ-8yQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 14, 2021 at 10:17 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Zhihong Yu <zyu(at)yugabyte(dot)com> writes:
> > I was looking at fmgr_internal_validator().
> > It seems prosrc is only used internally.
> > The patch frees the C string prosrc points to, prior to returning.
>
> There's really very little point in adding such code. Our memory
> context mechanisms take care of minor leaks like this, with less
> code and fewer cycles expended than explicit pfree calls require.
> It's worth trying to clean up explicitly in code that might get
> executed many times in a row, or might be allocating very big
> temporary chunks; but fmgr_internal_validator hardly falls in
> that category.
>
> regards, tom lane
>
Hi,
How about this occurrence which is in a loop ?
Thanks
Attachment | Content-Type | Size |
---|---|---|
c-str-free.patch | application/octet-stream | 431 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira | 2021-07-14 18:30:15 | Re: row filtering for logical replication |
Previous Message | Jacob Champion | 2021-07-14 18:23:59 | Re: PROXY protocol support |