Re: Use of OIDS as primary keys

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Bill Moran <wmoran(at)potentialtech(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Use of OIDS as primary keys
Date: 2002-05-14 06:02:52
Message-ID: 23545.1021356172@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> Do they actually save spaces (consider alignment issues and such)?

WITHOUT OIDS doesn't currently save any space --- the tuple header
layout is the same either way. It should save a few microseconds
per row inserted (since you don't have to generate an OID) but
that's about it.

The main reason for inventing the feature was to postpone OID-counter
wraparound in large installations. Wraparound isn't fatal, but can
be annoying --- for example, pg_dump may get confused about the best
order to dump tables in.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robert Abbate 2002-05-14 06:26:47 transitioning postgres oid
Previous Message Martijn van Oosterhout 2002-05-14 05:36:39 Re: Use of OIDS as primary keys