Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA02183 for ; Sun, 9 May 1999 13:12:29 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id NAA02366; Sun, 9 May 1999 13:11:22 -0400 (EDT) To: Bruce Momjian cc: Michael Olivier , pgsql-sql@postgreSQL.org Subject: Re: [SQL] keeping OID's when copying table In-reply-to: Your message of Sun, 9 May 1999 08:02:25 -0400 (EDT) <199905091202.IAA16745@candle.pha.pa.us> Date: Sun, 09 May 1999 13:11:21 -0400 Message-ID: <2364.926269881@sss.pgh.pa.us> From: Tom Lane Bruce Momjian writes: > OK, I think Tom Lane fixed this by generating an error in 6.5 beta. >> dmdemo=> INSERT INTO new_table (oid, mycol) SELECT oid, mycol FROM >> dmdemo-> old_table; >> INSERT 837644 1 Hmm, what version did you do this with? It would fairly reliably crash the backend in recent times, so a week or two ago I put in a temporary check to generate an error instead. I would like to see INSERT or UPDATE able to set the OID field; but we're too close to 6.5 release to think about making that work for 6.5. Right now the only way to preserve OIDs is to use COPY WITH OIDS. regards, tom lane