BUG #17106: Renaming system types is possible and it potentially leads to a crash

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 #17106: Renaming system types is possible and it potentially leads to a crash
Date: 2021-07-15 04:00:01
Message-ID: 17106-1bce73f14df54e7e@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: 17106
Logged by: Alexander Lakhin
Email address: exclusion(at)gmail(dot)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.)

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kyotaro Horiguchi 2021-07-15 05:22:35 Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
Previous Message Jeff Janes 2021-07-14 23:10:26 Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size