Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f870a3798821 for ; Thu, 6 Sep 2001 20:36:04 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f870ZOK17889; Thu, 6 Sep 2001 20:35:25 -0400 (EDT) To: Carolyn Lu Wong cc: pgsql-sql@postgresql.org Subject: Re: duplicated oid In-reply-to: <3B980C81.365226FF@greatpacific.com.au> References: <3B930A0A.64EC6D82@greatpacific.com.au> <3B980C81.365226FF@greatpacific.com.au> Comments: In-reply-to Carolyn Lu Wong message dated "Fri, 07 Sep 2001 09:53:37 +1000" Date: Thu, 06 Sep 2001 20:35:24 -0400 Message-ID: <17886.999822924@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200109/24 X-Sequence-Number: 4670 Carolyn Lu Wong writes: > anyone knows if duplicated oid is possible?? Yes, if you don't have a unique index on it and you've generated more than four billion rows in the database. > is there a possible way to remove the duplicate row, now that i don't > know which ID to use? any suggestions? Use ctid to distinguish the rows. Note ctid will change if you update a row, so it's not a permanent identifier either, but it will serve for deleting a row. regards, tom lane