Re: Using oids for fast read-only access? - Mailing list pgsql-general

From Christopher Zach
Subject Re: Using oids for fast read-only access?
Date
Msg-id 01081308151200.05248@fcggpc47.icg.tu-graz.ac.at
Whole thread Raw
In response to Re: Using oids for fast read-only access?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-general
Am Freitag, 10. August 2001 12:24 schrieben Sie:
> Christopher Zach writes:
> > After inserting the geometry, the data is read only, therefore I would
> > like to replace the id's in the rtree with oids (or anything that has a
> > constant time access).
>
> And what makes you think oids have a more "constant" access time than
> integers?  The only thing you will save if you omit the id column is
> space.
Because I thought the oid has some direct relationship to the physical page
the row is stored in. The intention was to jump directly to the row instead
of going through a btree...

> Oids aren't really any different than other (integer) types, only that
> they are generated automatically.
It seems so :( But how would you speed up many individual selects on
nonconsecutive rows?

bye,

Christopher Zach

pgsql-general by date:

Previous
From: Randall Perry
Date:
Subject: Re: Constraint, Rule, or Trigger?
Next
From: "Steve SAUTETNER"
Date:
Subject: Reading a table in a database from another database