OID vs SERIAL - Mailing list pgsql-general

From Jay Bloodworth
Subject OID vs SERIAL
Date
Msg-id 37C9BD7D.43F1E677@dokodiner.com
Whole thread Raw
Responses Re: [GENERAL] OID vs SERIAL
List pgsql-general
Seeking informed opinion on what is better to use as a unique row id for
linking tables together in a normalized database, a SERIAL field or the
pgsql OID.  This is for an intranet application with a small user base,
but I'd like to make it robust and scalable where it is easy to do so.
My conclusions so far:

OIDs:

Pros:
    * They're already there; save a couple bytes per row
    * Specific method to retrieve after INSERT (maybe faster than SELECT
on the sequence)

Cons:
    * Not serial by table; hard to build linked table 'by hand'
    * not pure SQL

SERIAL:

Pros:
    * Based on fairly vanilla SQL
    * Easier to reproduce all or part of a db on a dump/restore

Cons:
    * Performance?
    * Extra id field redundant

I'm sure I'm missing something, and I'm not entirely sure how to weight
the points I've got.  Advice appreciated.

Please CC me.  I subscribed to the digest.

Jay

pgsql-general by date:

Previous
From: Jay Bloodworth
Date:
Subject: SERIAL vs. OIDs
Next
From: Chris Bitmead
Date:
Subject: Re: [GENERAL] OID vs SERIAL