Re: BUG #14867: Cascade drop type error
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: gomer94@yandex.ru, pgsql-bugs@postgresql.org
Date: 2017-10-23T16:17:26Z
Lists: pgsql-bugs
On 2017-10-23 12:09:24 -0400, Tom Lane wrote: > gomer94@yandex.ru writes: > > CREATE TYPE my_type AS (f1 integer); > > CREATE TYPE my_type_2 AS (f2 my_type); > > CREATE TABLE my_table (c1 my_type_2); > > CREATE VIEW my_view AS SELECT ((C1).f2).f1 FROM my_table; > > DROP TYPE my_type CASCADE; > > Cute. Type my_type isn't exposed as a dependency of the view, > because it's only referenced internally in the expression tree > not as a result column type. We can fix that easily enough by > teaching dependency.c to log the result type of a FieldSelect > as a dependency. That does remind me of patch 0001 in http://archives.postgresql.org/message-id/20170314224706.nxvtapenky6eom3z%40alap3.anarazel.de - Andres
Commits
-
Fix some oversights in expression dependency recording.
- dde99de1169e 9.3.20 landed
- 900a9fd64a0c 9.2.24 landed
- f3ea3e3e820b 11.0 landed
- df4aa6e4e874 10.1 landed
- d8a3be52f44d 9.4.15 landed
- aa0518301fd8 9.5.10 landed
- 285b850d518d 9.6.6 landed