回复:BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true - Mailing list pgsql-bugs

From webbohan
Subject 回复:BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true
Date
Msg-id tencent_E7B3EB9BCD305CBF3C20AF141C782B8DB307@qq.com
Whole thread Raw
In response to BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
there is patch.
I have remove the meaningless code.


------------------ 原始邮件 ------------------
发件人: "webbohan" <noreply@postgresql.org>;
发送时间: 2025年10月5日(星期天) 上午10:29
收件人: "pgsql-bugs"<pgsql-bugs@lists.postgresql.org>;
抄送: "webbohan"<webbohan@qq.com>;
主题: BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true

The following bug has been logged on the website:

Bug reference:      19073
Logged by:          Webbo Han
Email address:      webbohan@qq.com
PostgreSQL version: 18.0
Operating system:   all
Description:       

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.

Attachment

pgsql-bugs by date:

Previous
From: Marco Boeringa
Date:
Subject: Potential "AIO / io workers" inter-worker locking issue in PG18?
Next
From: Markus KARG
Date:
Subject: Re: Potential "AIO / io workers" inter-worker locking issue in PG18?