Sorry. Interesting the workaround doesn't work in 7.2.X. Hopefully we will get this worked out in 7.4.
--------------------------------------------------------------------------- JMM Moi-Meme Maitre du Monde wrote: > Wrong ! The workaround works in 7.3 but is not backward compatible > with prior 7.x.y version. > > I began reverting to 7.2.3 :( Anyway, I will survive ;) > > On Thu, Dec 26, 2002 at 09:02:08AM +0100, JMM Moi-Meme Maitre du Monde wrote: > > Yes, it works. Thanks. > > > > I will just have to alter some 50 scripts, but that's better than > > having to revert my DBs (~18 GB) to 7.2.3 while waiting for 7.4. > > > > On Wed, Dec 25, 2002 at 10:58:41PM -0500, Bruce Momjian wrote: > > > > > > This is a known problem with 7.3.X. It doesn't create an oid column as > > > part of SELECT INTO .... > > > > > > We have a TODO item: > > > > > > * Fix SELECT ... INTO and CREATE TABLE AS to have appopriate OID column > > > > > > so this will be fixed, hopefully in 7.4. We couldn't fix it in 7.3.X > > > without causing more serious problems. If you specify the oid column as > > > part of the SELECT INTO, it will take the oid from the original table > > > and put it in your new table. Does that help you? > > > > -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
