Composite Type dependency bug

From: David Fetter <david(at)fetter(dot)org>
To: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Composite Type dependency bug
Date: 2005-07-15 01:16:50
Message-ID: 20050715011650.GD1199@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Folks,

Pardon the dup, but I couldn't post via the web site :/

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
--
David Fetter david(at)fetter(dot)org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778

Remember to vote!

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephan Szabo 2005-07-15 05:06:52 Re: BUG #1770: Composite type dependency broken
Previous Message Mars 2005-07-15 00:47:51 BUG #1771: re-connection to database error