Re: Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO
Date
Msg-id 25808.1043334208@sss.pgh.pa.us
Whole thread Raw
In response to Re: Call for objections: put back OIDs in CREATE TABLE  (Curt Sampson <cjs@cynic.net>)
Responses Re: Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO
List pgsql-hackers
Curt Sampson <cjs@cynic.net> writes:
> I object. I personally think we should be moving towards not using OIDs
> as the default behaviour, inasmuch as we can, for several reasons:

All these objections are global in nature, not specific to CREATE TABLE
AS.  The argument that persuaded me to do something here is that CREATE
TABLE AS should not be different from CREATE TABLE's default behavior.

I have no problem with moving towards lack-of-OIDs as the default
behavior for both statements, in the long run, if we can get past the
compatibility issues.  But I don't think OIDs in user tables are costing
us anything much, so I'm not prepared to take any big compatibility hit
to change the default ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Curt Sampson
Date:
Subject: Re: Threads
Next
From: Michael Meskes
Date:
Subject: Re: ECPG, threading and pooling