BUG #17106: Renaming system types is possible and it potentially leads to a crash - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #17106: Renaming system types is possible and it potentially leads to a crash
Date
Msg-id 17106-1bce73f14df54e7e@postgresql.org
Whole thread Raw
Responses Re: BUG #17106: Renaming system types is possible and it potentially leads to a crash
Re: BUG #17106: Renaming system types is possible and it potentially leads to a crash
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      17106
Logged by:          Alexander Lakhin
Email address:      exclusion@gmail.com
PostgreSQL version: 13.3
Operating system:   Ubuntu 20.04
Description:

While dropping system types is prohibited (say, you can't DROP TYPE void),
renaming is not. So the following commands lead to an inevitable crash.
ALTER TYPE void RENAME TO void_void;
CREATE TABLE void(id int);
CREATE EXTENSION pg_stat_statements;
SELECT pg_stat_statements_reset();

(Superuser rights required for this, though.)


pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size