Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: BUG #19470: PostgreSQL backend aborts (assert failure) when a prepared statement returns a composite type cast t
To: pgsql-bugs@lists.postgresql.org
From: PG Bug reporting form <noreply@postgresql.org>
Cc: haogangmao@gmail.com
Reply-To: haogangmao@gmail.com, pgsql-bugs@lists.postgresql.org
Date: Wed, 29 Apr 2026 11:27:19 +0000
Message-ID: <19470-0a344a5b356fc1a8@postgresql.org>
Auto-Submitted: auto-generated
Archived-At: <https://www.postgresql.org/message-id/19470-0a344a5b356fc1a8%40postgresql.org>
Precedence: bulk

The following bug has been logged on the website:

Bug reference:      19470
Logged by:          HaoGang Mao
Email address:      haogangmao@gmail.com
PostgreSQL version: 18.3
Operating system:   Linux
Description:       =20

Reproduction steps (minimal):
  BEGIN;
  CREATE TYPE foo AS (a int, b text);
  PREPARE p AS SELECT CAST(ROW(1, 'hello') AS foo)::text;
  EXECUTE p;
  ALTER TYPE foo ALTER ATTRIBUTE a TYPE VARCHAR(100);
  EXECUTE p;
  COMMIT;

Expected: Error message (type modified while a prepared plan / expression is
active)
Actual:   Server connection dropped; backend aborts with SIGABRT due to
assertion failure

Server log (trimmed):
  TRAP: failed Assert("false"), File: "heaptuple.c", Line: 1417, PID: <pid>
  ... heap_deform_tuple()