From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jonathan Bartlett <johnnyb6@sdf.lonestar.org>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: maximum number of rows in table - what about oid limits?
Date: Fri, 08 Jun 2001 10:38:02 -0400
Message-ID: <9559.992011082@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.21.0106071332360.781-100000@sdf.lonestar.org>
References: <Pine.LNX.4.21.0106071332360.781-100000@sdf.lonestar.org>
Jonathan Bartlett <johnnyb6@sdf.lonestar.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, johnnyb6@sdf.lonestar.org, josh@agliodbs.com
Subject: Re: maximum number of rows in table - what about oid limits?
In-Reply-To: <9559.992011082@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox