Re: DROP COLUMN

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Rod Taylor" <rbt(at)zort(dot)ca>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: DROP COLUMN
Date: 2002-07-16 03:46:30
Message-ID: GNELIHDDFBOCMGBFGEFOEECKCDAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Excellent idea. That's how temp tables worked, by bypassing the
> > syscache. I wonder if you could just prevent dropped columns from being
> > returned by the syscache. That may work just fine.
>
> No, it will break all the places that need to see dropped columns.
>
> I agree that a wrapper function is probably an appropriate solution,
> but only some of the calls of SearchSysCache should use it.

What like add another parameter to SearchSysCache*?

Another question: How do I fill out the ObjectAddress when trying to drop
related objects?

eg:

object.classId = ??;
object.objectId = ??;
object.objectSubId = ??;

performDeletion(&object, behavior);

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-07-16 04:01:41 Re: [PATCHES] CLUSTER not lose indexes
Previous Message Bruce Momjian 2002-07-16 03:33:48 Re: line datatype