Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f58EdhE11613 for ; Fri, 8 Jun 2001 10:39:43 -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 f58Ec2R09562; Fri, 8 Jun 2001 10:38:02 -0400 (EDT) To: Jonathan Bartlett cc: Josh Berkus , pgsql-sql@postgresql.org Subject: Re: maximum number of rows in table - what about oid limits? In-reply-to: References: Comments: In-reply-to Jonathan Bartlett message dated "Thu, 07 Jun 2001 13:34:24 -0000" Date: Fri, 08 Jun 2001 10:38:02 -0400 Message-ID: <9559.992011082@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/121 X-Sequence-Number: 3341 Jonathan Bartlett writes: > Besides compatibility, what breaks when you make OIDs/Txn IDs > INT8s? OIDs are part of the on-the-wire protocol (column type data returned during a SELECT is in the form of OIDs). So extending OIDs to int8 would pose nontrivial client/server compatibility hazards. > Maybe there should be a minor fork called Postgres64 which does > this for those needing large tables. I've been thinking it should be a compile-time option. But the protocol issue is going to be a problem. regards, tom lane