I am currently testing a fix that allows you to say ALTER TABLE DROP COLUMN oid; which will behave the same way a regular user-column DROP would.
I intend to interpret SET WITHOUT OIDS as DROP COLUMN oid RESTRICT.
Will it handle this case:
usa=# create table testy (a int4) without oids;
CREATE TABLE
usa=# alter table testy add oid int4;
ALTER TABLE
usa=# \d testy
Table "public.testy"
Column | Type | Modifiers
--------+---------+-----------
a | integer |
oid | integer |How about the syntax:
ALTER TABLE t DROP OIDS;
This I can make:
ALTER TABLE t DROP CLUSTER;
Chris
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
