Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f57260E19595; Wed, 6 Jun 2001 22:06:00 -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 f5725qR06633; Wed, 6 Jun 2001 22:05:52 -0400 (EDT) To: john@august.com cc: Stephan Szabo , pgsql-general@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [SQL] maximum number of rows in table - what about oid limits? In-reply-to: <20010607010814.72573.qmail@web10005.mail.yahoo.com> References: <20010607010814.72573.qmail@web10005.mail.yahoo.com> Comments: In-reply-to John Scott message dated "Wed, 06 Jun 2001 18:08:14 -0700" Date: Wed, 06 Jun 2001 22:05:52 -0400 Message-ID: <6630.991879552@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/217 X-Sequence-Number: 10552 John Scott writes: > but does retrying fix the problem? wouldn't the second try just often > see the same oid again. does a failed attempt increment the oid???? Yes. > by the way, have you written anything up on the txid wrapping problem? > we talked about this at osdn last year in san jose. i proposed > 64 bits, and you discussed a clever wrapping algorithm involving 48 bits and, > if memory serves me, backward compatiablility of the disk format. The wraparound idea was discussed on pghackers; people didn't like it much, but I haven't heard a better near-term solution ... regards, tom lane