pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
Cc: sqllist <pgsql-sql@postgresql.org>
Cc: Jeff MacDonald <jeff@pgsql.com>
Subject: Re: OID Perfomance - Object-Relational databases
Date: Tue, 03 Oct 2000 17:33:15 -0700
Message-ID: <39DA7ACB.EA4D0B3E@agliodbs.com> (raw)
References: <39DA03EA.7A1027E8@agliodbs.com>
	<29675.970600245@sss.pgh.pa.us>

Tom,

> By and large I'd recommend using a serial column in preference to OIDs,
> though, for two reasons:
> 
> 1. dump/restore is more practical that way (don't have to worry about
>    saving/reloading OIDs).
> 
> 2. counter overflow problems hit you only per-table, not
>    per-installation.

Hmmm ... for some tables, switching to Serial would work.  However, one
of the things I've done is add universal mod_data (modification stats)
and notes tables, which have to relate via OID because they relate to
5-7 different tables.  To wit:

CREATE TABLE notes AS (
	ref_OID		OID,
	staff_OID	OID	REFERENCES staff,
	note_date	DATE,
	note_text	TEXT
	)

And the ref_oid relates to any of 5 different tables, thus allowing a
single table to hold notes on clients, candidates, bills, etc.  Very
elegant, and using serials instead of the OID not possible.

SO I'm concerned about the problems you mentioned above.  pg_dump has a
-o option; are there problems with this?  And how liekly are counter
overflow problems?
	
Josh Berkus
	


-- 
______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



view thread (21+ messages)  latest in thread

Message-ID: <39DA7ACB.EA4D0B3E@agliodbs.com>
Permalink:  ../39DA7ACB.EA4D0B3E@agliodbs.com/
Also on:    postgresql.org/message-id/39DA7ACB.EA4D0B3E@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, jeff@pgsql.com
  Subject: Re: OID Perfomance - Object-Relational databases
  In-Reply-To: <39DA7ACB.EA4D0B3E@agliodbs.com>
  References: <39DA03EA.7A1027E8@agliodbs.com> <29675.970600245@sss.pgh.pa.us> <39DA7ACB.EA4D0B3E@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