BUG #1770: Composite type dependency broken - Mailing list pgsql-bugs

From David Fetter
Subject BUG #1770: Composite type dependency broken
Date
Msg-id 20050715003008.742F9F0B0C@svr2.postgresql.org
Whole thread Raw
Responses Re: BUG #1770: Composite type dependency broken  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
Re: BUG #1770: Composite type dependency broken  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      1770
Logged by:          David Fetter
Email address:      david@fetter.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

pgsql-bugs by date:

Previous
From: "Mars"
Date:
Subject: BUG #1771: re-connection to database error
Next
From: Stephan Szabo
Date:
Subject: Re: BUG #1770: Composite type dependency broken