The following bug has been logged online:

Bug reference: 1770
Logged by: David Fetter
Email address: david (AT) fetter (DOT) org
PostgreSQL version: 8.0.3
Operating system: Linux
Description: Composite type dependency broken
Details:

Here's a repro (psql):

create table foo (foo_id SERIAL PRIMARY KEY, foo_text TEXT NOT NULL);
CREATE type two_foos AS (foo1 foo, foo2 foo);
CREATE type four_foos AS (two_foo1 two_foos, two_foo2 two_foos);
DROP TABLE foo CASCADE;

Perhaps I have misunderstood, but I would think that both two_foos and
four_foos would disappear as a result of this. They don't :/

Cheers,
D

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

On Fri, 15 Jul 2005, David Fetter wrote:

I think the current definition is that the columns of the removed type
disappear, which means two_foos becomes a type with no columns rather than
it being removed.



---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

"David Fetter" <david (AT) fetter (DOT) org> writes:
No; their columns disappear, but the types don't. This is just the same
as not trashing an entire table when a single column's type is dropped
--- that propagates as a DROP COLUMN, not a DROP TABLE.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match