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

Поиск
Список
Период
Сортировка
Искать
От
Julien Rouhaud
Тема
Re: Avoid redudant initialization and possible memory leak (src/backend/parser/parse_relation.c)
Дата
Msg-id
20220913140556.6ot7awymd2jyxnkz@jrouhaud
Ответ на
Список
Дерево обсуждения
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 Tue, Sep 13, 2022 at 10:21:22AM -0300, Ranier Vilela wrote:
> Hi,
>
> The commit: Revert SQL/JSON features
> https://github.com/postgres/postgres/commit/2f2b18bd3f554e96a8cc885b177211be12288e4a
>
> Left a little oversight.
> I believe it will be properly corrected when it is applied again.
> However, for Postgres 15 this may can cause a small memory leak.

It's not a memory leak, the chunk will be freed eventually when the owning
memory context is reset, but I agree that one of the two identical
initializations should be removed.


В списке pgsql-hackers по дате отправления
От: Tom Lane
Дата:
Сообщение: Re: Splitting up guc.c
От: Alvaro Herrera
Дата:
FAQ