Re: BUG #14867: Cascade drop type error

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: gomer94(at)yandex(dot)ru, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14867: Cascade drop type error
Date: 2017-10-23 16:17:26
Message-ID: 20171023161726.5hr6rs56hxn67zz2@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2017-10-23 12:09:24 -0400, Tom Lane wrote:
> gomer94(at)yandex(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-10-23 16:33:52 Re: BUG #14867: Cascade drop type error
Previous Message Tom Lane 2017-10-23 16:09:24 Re: BUG #14867: Cascade drop type error