Skip site navigation (1) Skip section navigation (2)

BUG #1770: Composite type dependency broken

From: "David Fetter" <david(at)fetter(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1770: Composite type dependency broken
Date: 2005-07-15 00:30:08
Message-ID: 20050715003008.742F9F0B0C@svr2.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
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

Responses

pgsql-bugs by date

Next:From: MarsDate: 2005-07-15 00:47:51
Subject: BUG #1771: re-connection to database error
Previous:From: Alvaro HerreraDate: 2005-07-14 20:57:07
Subject: Re: BUG #1768: to_char result of an interval differs between 7.x and 8.x

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group