| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO |
| Date: | 2003-01-22 05:32:52 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOKECMCFAA.chriskl@familyhealth.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org]On Behalf Of Tom Lane
> Sent: Wednesday, 22 January 2003 4:12 AM
> To: pgsql-hackers(at)postgresql(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hans-Jürgen Schönig | 2003-01-22 06:53:31 | Re: [mail] Re: Win32 port patches submitted |
| Previous Message | Christopher Kings-Lynne | 2003-01-22 05:29:33 | Re: What goes into the security doc? |