pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: sqllist <pgsql-sql@postgresql.org>
Subject: Concerns about the OID
Date: Mon, 02 Oct 2000 08:39:42 -0700
Message-ID: <39D8AC3E.A8E2C8BF@agliodbs.com> (raw)

Folks,

	I'm made rather extensive use of PGSQL's universal OID in my database
design.  However, now that I'm building the interface for my first
transaction datbase in PGSQL, I'm concerned about a couple of things:

1. Has anyone experienced any performance problems relating
tables/classes via OID?

2. Can I add an index on OIDs for a particular table?

3. Int4 seems sort of small for a number that has to uniquely identify
every object in the database.  Are there plans to expand the OID to
Int8?

-Josh

-- 
______AGLIO DATABASE SOLUTIONS___________________________
                                        Josh Berkus
   Complete information technology      josh@agliodbs.com
    and data management solutions       (415) 436-9166
   for law firms, small businesses       fax  436-0137
    and non-profit organizations.       pager 338-4078
                        		San Francisco



Message-ID: <39D8AC3E.A8E2C8BF@agliodbs.com>
Permalink:  ../39D8AC3E.A8E2C8BF@agliodbs.com/
Also on:    postgresql.org/message-id/39D8AC3E.A8E2C8BF@agliodbs.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: josh@agliodbs.com
  Subject: Re: Concerns about the OID
  In-Reply-To: <39D8AC3E.A8E2C8BF@agliodbs.com>
  References: <39D8AC3E.A8E2C8BF@agliodbs.com>

* 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