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

From PG Bug reporting form
Subject BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true
Date
Msg-id 19073-93772b97a2f1ecf3@postgresql.org
Whole thread Raw
Responses 回复:BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true
Re: BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true
List pgsql-bugs
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.


pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: [BUGS] BUG #11500: PRIMARY KEY index not being used
Next
From: PG Bug reporting form
Date:
Subject: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases