Re: deprecating the use of OIDs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: deprecating the use of OIDs
Date
Msg-id 13320.1064879119@sss.pgh.pa.us
Whole thread Raw
In response to Re: deprecating the use of OIDs  (Neil Conway <neilc@samurai.com>)
List pgsql-hackers
Neil Conway <neilc@samurai.com> writes:
> On Mon, 2003-09-29 at 18:37, Tom Lane wrote:
>> It doesn't seem to me that this really buys much.  What we really want
>> is a way for a dump/reload to remove OIDs from tables that formerly had
>> them; otherwise people will not easily be able to migrate their existing
>> tables away from having OIDs.

> Can't they just use ALTER TABLE ... WITHOUT OIDS?

That's true --- I'd forgotten we had that.

>>> ... and a single SET can apply to
>>> multiple CREATE TABLEs.
>> 
>> Not unless you want partial pg_restores to break.

> So is it worth doing this rather than WITH/WITHOUT OIDS, then?

[shrug]  It seems quite cosmetic to me.  What might be more useful is
an option to keep pg_dump from saying either WITH OIDS or WITHOUT OIDS,
probably as part of a more general "suppress Postgres-isms" option.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Christopher Browne
Date:
Subject: Re: 2-phase commit
Next
From: Tom Lane
Date:
Subject: Re: deprecating the use of OIDs