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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17106: Renaming system types is possible and it potentially leads to a crash
Date: 2021-07-15 07:42:16
Message-ID: YO/m2HKz7JdsqE/t@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Jul 15, 2021 at 04:00:01AM +0000, PG Bug reporting form wrote:
> 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.)

Like one of those many stupid things one can do as a superuser :)

This does not seem worth worrying about to me.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-07-15 08:28:02 BUG #17107: pspg packages not properly signed
Previous Message Kyotaro Horiguchi 2021-07-15 07:33:48 Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size