Re: DROP COLUMN misbehaviour with multiple inheritance

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)atentus(dot)com>, <hannu(at)tm(dot)ee>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: DROP COLUMN misbehaviour with multiple inheritance
Date: 2002-09-20 03:38:00
Message-ID: GNELIHDDFBOCMGBFGEFOIEFKCEAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> > The decision at hand is whether to apply a patch. You cannot say "we're
> > not deciding now", because that is a decision...
>
> Yes. I am saying we should not assume we are going to remove multiple
> inheritance. We should apply the patch and make things a good as they
> can be for 7.3.

I think the patch should be applied. That way people who are using multiple
inheritance (if there are any) can know that they have a vaguely bug free
implementation in 7.3 until they redo their stuff for 7.4.

Chris

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Sherry 2002-09-20 03:47:40 Re: Postgres 7.2.2 Segment Error
Previous Message Bruce Momjian 2002-09-20 03:32:35 Re: DROP COLUMN misbehaviour with multiple inheritance

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2002-09-20 03:39:09 Re: CREATE DOMAIN doc fix
Previous Message Bruce Momjian 2002-09-20 03:32:35 Re: DROP COLUMN misbehaviour with multiple inheritance