Re: BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true
От | Euler Taveira |
---|---|
Тема | Re: BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true |
Дата | |
Msg-id | 5b04da16-c2de-464b-8677-9e4991b28e55@app.fastmail.com обсуждение исходный текст |
Ответ на | BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true (PG Bug reporting form <noreply@postgresql.org>) |
Ответы |
Re: BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true
|
Список | pgsql-bugs |
On Sat, Oct 4, 2025, at 11:29 PM, PG Bug reporting form wrote: > In function _SPI_execute_plan(), `my_tuptable` is local variable and > initialized as NULL. > If plan is canSetTag subqueries, `SPI_freetuptable(my_tuptable)` is > meaningless, because `my_tuptable` is NULL. > We'd better remove this code. > There could be multiple statements. The first case will call SPI_freetuptable() and it is a noop. The code path you are referring to is inside a foreach loop and a previous statement might set my_tuptable and needs to be freed before reusing it. That's exactly what the comment says. /* * The last canSetTag query sets the status values returned to the * caller. Be careful to free any tuptables not returned, to * avoid intra-transaction memory leak. */ if (canSetTag) { my_processed = _SPI_current->processed; SPI_freetuptable(my_tuptable); my_tuptable = _SPI_current->tuptable; my_res = res; } -- Euler Taveira EDB https://www.enterprisedb.com/
В списке pgsql-bugs по дате отправления: