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

Re: Problem with dump/restore and inheritance

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: (view raw, whole thread or download thread mbox)
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
  SRA OSS, Inc.

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-bugs by date

Next:From: prabuDate: 2006-02-25 07:11:27
Subject: BUG #2280: how to store images
Previous:From: Bruce MomjianDate: 2006-02-24 18:54:23
Subject: Re: BUG #2268: initdb fails to initialize database cluster with

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