From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Happy column dropping |
Date: | 2000-01-23 04:26:32 |
Message-ID: | 200001230426.XAA06789@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> [Charset ISO-8859-1 unsupported, filtering to ASCII...]
> > With caveats, it is now possible to drop columns from tables.
> >
> > The implementation is based on copying the old table to a new one minus
> > the specified column. This procedure changes the oids of everyone
> > involved, so I was wondering if
> > a) this is a good reason to tell people to stop using oids as keys, or
> > b) if there is some way to keep the oids on both the records and the
> > pg_class entry.
>
> Actually CLUSTER has the same problem, I think. It may be even worse
> because it drops all indexes. Can you take a look at that code too.
> Some people have reported problems with it, while others are OK. There
> is a cluster TODO mail file in the source tree. It shows an actual bug
> that still exists, plus some other issues with cluster.
>
I wonder if we should throw out a NOTICE when we drop some
characteristic of a table?
--
Bruce Momjian | http://www.op.net/~candle
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 | Tom Lane | 2000-01-23 04:38:11 | Re: [HACKERS] Happy column dropping |
Previous Message | The Hermit Hacker | 2000-01-23 04:23:16 | Re: [HACKERS] Happy column dropping |