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

Поиск
Список
Период
Сортировка
Искать
От
Alvaro Herrera
Тема
Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c)
Дата
Msg-id
20220914135643.lwzeu55resa3fkgd@alvherre.pgsql
Ответ на
Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c) (Ranier Vilela)
Список
Дерево обсуждения
Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c) Ranier Vilela <ranier.vf@gmail.com>
Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c) Julien Rouhaud <rjuju123@gmail.com>
Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c) Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c) Ranier Vilela <ranier.vf@gmail.com>
Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c) Alvaro Herrera <alvherre@alvh.no-ip.org> 
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/
В списке pgsql-hackers по дате отправления
Предыдущее
От: Imseih (AWS), Sami
Дата:
Следующее
От: Tom Lane
Дата:
FAQ