Re: DROP COLUMN misbehaviour with multiple inheritance

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: "Matthew T(dot) OConnor" <matthew(at)zeut(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hannu Krosing <hannu(at)tm(dot)ee>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: DROP COLUMN misbehaviour with multiple inheritance
Date: 2002-09-12 17:07:10
Message-ID: Pine.LNX.4.33.0209121106250.11324-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Thu, 12 Sep 2002, scott.marlowe wrote:

> Agreed.
>
> Actually, an argument could likely be made that changes that require
> initdb should be done as early as possible since the later the change the
> more people there will be to test the change, and there will be fewer
> people who actually have to initdb since a lot of folks don't test beta
> releases until the 3rd or 4th beta.

My mental dyslexia strikes again, that should be:

... since the EARLIER the change the more people there will be to test the
change, ...

sheesh. Sorry...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Elphick 2002-09-12 17:08:37 Re: OPAQUE and 7.2-7.3 upgrade
Previous Message Kris Jurka 2002-09-12 17:02:28 Re: Patch for getBestRowIdentifier (for testing with Oracle

Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2002-09-13 01:14:14 Re: DROP COLUMN misbehaviour with multiple inheritance
Previous Message scott.marlowe 2002-09-12 16:23:53 Re: DROP COLUMN misbehaviour with multiple inheritance