| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rod Taylor <rbt(at)zort(dot)ca>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP COLUMN |
| Date: | 2002-07-16 05:04:24 |
| Message-ID: | 200207160504.g6G54Oc15845@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christopher Kings-Lynne wrote:
> > > In fact, looking at it logically...if all the commands currently are
> > > required to check that they're not modifiying a system column,
> > then why not
> > > add the requirement that they must also not modify dropped
> > columns? I can
> > > do a careful doc search and try to make sure I've touched everything...
> >
> > Makes sense. Of course, we could make a syscache that didn't return
> > system columns either.
>
> Actually - are you certain that every command uses a SearchSysCache and not
> some other weirdness? If we have to do the odd exception, then maybe we
> should do them all as 'exceptions'?
I actually don't know. I know all the table name lookups do use
syscache or temp tables wouldn't have worked. ;-)
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2002-07-16 05:04:52 | Re: Unused system table columns |
| Previous Message | Christopher Kings-Lynne | 2002-07-16 05:03:14 | Re: DROP COLUMN |