Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f58EfZE14587 for ; Fri, 8 Jun 2001 10:41:35 -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.3/8.11.3) with ESMTP id f58EfMR09579; Fri, 8 Jun 2001 10:41:26 -0400 (EDT) To: "Tim Barnard" cc: pgsql-general@postgresql.org Subject: Re: Re: [SQL] maximum number of rows in table - what about oid limits? In-reply-to: <003b01c0ef63$aa67bd20$a519af3f@hartcomm.com> References: <20010606215234.97024.qmail@web10001.mail.yahoo.com> <6257.991867020@sss.pgh.pa.us> <003b01c0ef63$aa67bd20$a519af3f@hartcomm.com> Comments: In-reply-to "Tim Barnard" message dated "Thu, 07 Jun 2001 08:08:09 -0700" Date: Fri, 08 Jun 2001 10:41:22 -0400 Message-ID: <9576.992011282@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/277 X-Sequence-Number: 10614 "Tim Barnard" writes: > > If it does happen, you can just retry the failed object-creation > command until you get a nonconflicting OID assignment. > > Tom, or anyone who'd know for that matter, what is the > exact error I would need to look for? It'd be a complaint about attempt to insert a duplicate key into the unique index on one of several system catalogs' OID columns. There wouldn't be any earlier detection of the problem than that. regards, tom lane