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

From Christopher Kings-Lynne
Subject Re: Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO
Date
Msg-id GNELIHDDFBOCMGBFGEFOKECMCFAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO
List pgsql-hackers
Why don't you just include them by default, otherwise if WITHOUT OIDS
appears in the CREATE TABLE command, then don't include them ?

Chris

> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Tom Lane
> Sent: Wednesday, 22 January 2003 4:12 AM
> To: pgsql-hackers@postgresql.org
> Subject: [HACKERS] Call for objections: put back OIDs in CREATE TABLE
> AS/SELECT INTO
>
>
> We've gotten a couple of complaints now about the fact that 7.3 doesn't
> include an OID column in a table created via CREATE TABLE AS or SELECT
> INTO.  Unless I hear objections, I'm going to revert it to including an
> OID, and back-patch the fix for 7.3.2 as well.  See discussion a couple
> days ago on pgsql-general, starting at
> http://archives.postgresql.org/pgsql-general/2003-01/msg00669.php
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>



pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: What goes into the security doc?
Next
From: Hans-Jürgen Schönig
Date:
Subject: Re: [mail] Re: Win32 port patches submitted