BUG #18449: Altering column type fails when an SQL routine depends on the column

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: exclusion(at)gmail(dot)com
Subject: BUG #18449: Altering column type fails when an SQL routine depends on the column
Date: 2024-04-27 04:00:01
Message-ID: 18449-f8248467aaa294d5@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18449
Logged by: Alexander Lakhin
Email address: exclusion(at)gmail(dot)com
PostgreSQL version: 16.2
Operating system: Ubuntu 22.04
Description:

The following script:
CREATE TABLE t(a int, b varchar);
CREATE FUNCTION f(i int) RETURNS text LANGUAGE SQL
RETURN (SELECT b FROM t WHERE a = $1);

ALTER TABLE t ALTER COLUMN b TYPE text;
fails with:
ERROR: unexpected object depending on column: function f(integer)

on REL_14_STABLE .. master since e717a9a18.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-04-27 06:02:26 BUG #18450: The memory usage of the postgresql12.6 walsender process is abnormally high.
Previous Message Peter Geoghegan 2024-04-26 22:20:56 Re: BUG #17257: (auto)vacuum hangs within lazy_scan_prune()