From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chris Dunlop <chris(at)onthe(dot)net(dot)au>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Problem with dump/restore and inheritance |
Date: | 2006-02-25 03:40:31 |
Message-ID: | 200602250340.k1P3eV815486@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tom Lane wrote:
> Chris Dunlop <chris(at)onthe(dot)net(dot)au> writes:
> > One way or the other, I think either allowing the inherited
> > constraints to be dropped, or the inability of pg_dump to
> > correctly dump the resulting schema, should be considered a bug
> > rather than a lacking feature, as the current situation results
> > in problematical restores. Is there a "known bugs" list?
>
> I agree that allowing inherited constraints to be dropped is a bug.
> We don't really have a "known bugs" list other than the TODO list,
> which presently includes
>
> o %Disallow dropping of an inherited constraint
> o %Prevent child tables from altering or dropping constraints
> like CHECK that were inherited from the parent table
>
> (Which looks a bit redundant to me, but that's what Bruce has listed.)
Thanks, first one removed.
--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | prabu | 2006-02-25 07:11:27 | BUG #2280: how to store images |
Previous Message | Bruce Momjian | 2006-02-24 18:54:23 | Re: BUG #2268: initdb fails to initialize database cluster with |