Re: bug in 7.4 SET WITHOUT OIDs - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: bug in 7.4 SET WITHOUT OIDs
Date
Msg-id 4060E73B.2010705@familyhealth.com.au
Whole thread Raw
In response to Re: bug in 7.4 SET WITHOUT OIDs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: bug in 7.4 SET WITHOUT OIDs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> 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



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Chapter on PostreSQL in a book
Next
From: Neil Conway
Date:
Subject: Re: linked list rewrite