From: | jian he <jian(dot)universality(at)gmail(dot)com> |
---|---|
To: | Jelte Fennema <me(at)jeltef(dot)nl> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Support prepared statement invalidation when result types change |
Date: | 2023-08-29 09:29:43 |
Message-ID: | CACJufxF_-F0cUuuO08zV+KwbV7JFCJFPsLzcRvYQcY8F0WvqZA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 29, 2023 at 12:51 AM Jelte Fennema <me(at)jeltef(dot)nl> wrote:
>
> Could you share the full set of commands that cause the reporting
> issue? I don't think my changes should impact this reporting, so I'm
> curious if this is a new issue, or an already existing one.
I didn't apply your v2 patch.
full set of commands:
--------------------
regression=# CREATE TEMP TABLE pcachetest AS SELECT * FROM int8_tbl;
SELECT 5
regression=# PREPARE prepstmt2(bigint) AS SELECT * FROM pcachetest
WHERE q1 = $1;'
PREPARE
regression=# alter table pcachetest rename q1 to x;
ALTER TABLE
regression=# EXECUTE prepstmt2(123);
2023-08-29 17:23:59.148 CST [1382074] ERROR: column "q1" does not
exist at character 61
2023-08-29 17:23:59.148 CST [1382074] HINT: Perhaps you meant to
reference the column "pcachetest.q2".
2023-08-29 17:23:59.148 CST [1382074] STATEMENT: EXECUTE prepstmt2(123);
ERROR: column "q1" does not exist
HINT: Perhaps you meant to reference the column "pcachetest.q2".
--------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Zhijie Hou (Fujitsu) | 2023-08-29 09:44:54 | RE: logical_replication_mode |
Previous Message | Daniel Gustafsson | 2023-08-29 09:26:13 | Re: Standardize spelling of "power of two" |