Re: DROP COLUMN - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: DROP COLUMN
Date
Msg-id 200207160438.g6G4cnY05686@candle.pha.pa.us
Whole thread Raw
In response to Re: DROP COLUMN  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: DROP COLUMN  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Re: DROP COLUMN  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> "Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> >> 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*?
> 
> Definitely *not*; I don't want to kluge up every call to SearchSysCache
> with a feature that's only relevant to a small number of them.

Uh, then what?  The only idea I had was to set a static boolean variable in
syscache.c that controls whether droppped columns are returned, and have
a enable/disable functions that can turn it on/off.  The only problem is
that an elog inside a syscache lookup would leave that value set.

My only other idea is to make a syscache that is like ATTNAME except
that it doesn't return a dropped column.  I could probably code that up
if you wish.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: bit type external representation
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Re: DROP COLUMN