public inbox for pgsql-bugs@postgresql.org  

help / color / mirror / Atom feed

From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: haogangmao@gmail.com
Subject: BUG #19469: Prevent SIGSEGV on FETCH after ALTER TYPE of cursor rowtype
Date: Mon, 27 Apr 2026 10:53:54 +0000
Message-ID: <19469-e7612f56d0e1ce34@postgresql.org> (raw)

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:        

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;
```

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, haogangmao@gmail.com
  Subject: Re: BUG #19469: Prevent SIGSEGV on FETCH after ALTER TYPE of cursor rowtype
  In-Reply-To: <19469-e7612f56d0e1ce34@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox