Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: BUG #19469: Prevent SIGSEGV on FETCH after ALTER TYPE of cursor rowtype
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: Mon, 27 Apr 2026 10:53:54 +0000
Message-ID: <19469-e7612f56d0e1ce34@postgresql.org>
Auto-Submitted: auto-generated
Archived-At: <https://www.postgresql.org/message-id/19469-e7612f56d0e1ce34%40postgresql.org>
Precedence: bulk

The following bug has been logged on the website:

Bug reference:      19469
Logged by:          HaoGang Mao
Email address:      haogangmao@gmail.com
PostgreSQL version: 17.3
Operating system:   OS: Linux (Docker)
Description:       =20

An open cursor can continue returning tuples built with the old physical
layout of a named composite type. If that type is changed in the same
transaction (for example ALTER TYPE ... ALTER ATTRIBUTE ... TYPE), a later
FETCH may format the tuple using updated descriptor and output metadata.

Minimal Reproduction SQL:
```sql
CREATE TYPE foo AS (a INT, b INT);
BEGIN;
DECLARE c CURSOR FOR
  SELECT (i, power(2, 30))::foo
  FROM generate_series(1,10) i;
FETCH c;
ALTER TYPE foo ALTER ATTRIBUTE b TYPE TEXT;
FETCH c;
COMMIT;
```