| From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Wacky OID idea |
| Date: | 2002-08-05 07:27:15 |
| Message-ID: | 87r8hdlq98.fsf@klamath.dyndns.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)atentus(dot)com> writes:
> Christopher Kings-Lynne dijo:
> > Could we overload "ALTER TABLE/DROP COLUMN oid" to allow someone to change a
> > table to be WITHOUT OIDs at runtime?
I don't think it would be easy to do this without rewriting the table,
as Alvaro suggested. And if you're going to give this DROP COLUMN
variant totally different behavior from any other form of DROP COLUMN,
ISTM that it doesn't belong with DROP COLUMN.
That said, being able to remove the OIDs from a table would be fairly
useful, IMHO.
> Create new filenode, copy tuples over, change relhasoids. Seems easy.
> Am I missing something?
Yes -- DROP COLUMN currently doesn't require that the entire table be
re-written, it just modifies some meta-data.
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-08-05 07:36:19 | Re: Wacky OID idea |
| Previous Message | Dave Page | 2002-08-05 07:20:58 | Re: FUNC_MAX_ARGS benchmarks |