Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c)

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c)
Date: 2022-09-14 13:56:43
Message-ID: 20220914135643.lwzeu55resa3fkgd@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-Sep-13, Ranier Vilela wrote:

> Yeah, as per Julien's answer, there is really no memory leak, but just
> unnecessary double execution of pstrdup.
> But for Postgres 15, I believe it's worth avoiding this, because it's
> wasted cycles.

Yeah, this is a merge mistake. Fix applied, thanks.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-09-14 14:10:39 Re: FTS parser - missing UUID token type
Previous Message Imseih (AWS), Sami 2022-09-14 13:20:09 Re: Query Jumbling for CALL and SET utility statements