BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: webbohan(at)qq(dot)com
Subject: BUG #19073: there are meaningless code in _SPI_execute_plan() when canSetTag is true
Date: 2025-10-05 02:29:34
Message-ID: 19073-93772b97a2f1ecf3@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 19073
Logged by: Webbo Han
Email address: webbohan(at)qq(dot)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.

Responses

Browse pgsql-bugs by date

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