Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2023-06-26T08:35:44Z
Lists: pgsql-bugs
On Mon, Jun 26, 2023 at 08:00:01AM +0000, PG Bug reporting form wrote: > But if the access method was set during a matview creation, it's deletion > is > prevented as expected: > CREATE ACCESS METHOD heap2 TYPE TABLE HANDLER heap_tableam_handler; > CREATE MATERIALIZED VIEW heapmv USING heap2 AS SELECT 1::int; > DROP ACCESS METHOD heap2; > ERROR: cannot drop access method heap2 because other objects depend on it > DETAIL: materialized view heapmv depends on access method heap2 > HINT: Use DROP ... CASCADE to drop the dependent objects too. > > Reproduced on REL_15_STABLE .. master. Thanks for the report! ALTER TABLE .. SET ACCESS METHOD is on me. Will look.. -- Michael
Commits
-
Fix pg_depend entry to AMs after ALTER TABLE .. SET ACCESS METHOD
- 93401ec02f40 15.4 landed
- 97d89101045f 16.0 landed