Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS - Mailing list pgsql-hackers

From Greg Stark
Subject Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS
Date
Msg-id BCB8D4DC-4255-4168-A94C-C9D07403B94B@enterprisedb.com
Whole thread Raw
In response to Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Well for one thing because they don't scale well to billions of  
records. For another they're even less like the standard or anything  
any other database has.

I agree with you that there's no reason to actively deprecate OIDs or  
hurt users who use them. But we should make it as easy as possible for  
users who want to move to a normal primary key, not put obstacles in  
their way like large full table rewrites.

-- 
Greg


On 10 Feb 2009, at 01:49, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Greg Stark <stark@enterprisedb.com> writes:
>> I think what you propose would be a mistake. We want to encourage
>> people to move *away* from OIDS.
>
> Why?  I don't agree with that premise, and therefore not with any
> of the rest of your argument.
>
>            regards, tom lane


pgsql-hackers by date:

Previous
From: Bernd Helmle
Date:
Subject: Re: temporarily stop autovacuum
Next
From: Greg Stark
Date:
Subject: Re: Optimization rules for semi and anti joins