pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steve Wampler <swampler@noao.edu>
To: Thomas Swan <tswan@olemiss.edu>
Cc: Michael Teter <michael_teter@yahoo.com>
Cc: Poet/Joshua Drake <poet@linuxports.com>
Cc: postgres-sql <pgsql-sql@postgresql.org>
Subject: Re: Using a postgres table to maintain unique id?
Date: Tue, 14 Nov 2000 10:44:53 -0700
Message-ID: <3A117A15.6A247634@noao.edu> (raw)
References: <5.0.0.25.0.20001114113001.00aad5f8@sunset.backbone.olemiss.edu>

Thomas Swan wrote:
> 
> At 11/13/2000 06:22 PM -0800, Michael Teter wrote:
> >
> > From what I can tell (both from docs and doing a
> > describe on sequences in my database), a postgresql
> > sequence is an int4, not an int8, and thus you are
> > limited to a max of 2.1 billion values.
> >
> > If you require an int8 sequence, you'll probably have
> > to manage your own and just use an int8 column.
> >
> I had originally started using int8 and creating custom sequences.   However,
> as mentioned in a previous post, there is an inherent performance penalty in
> using int8 over int4.   Tom Lane advised me that the int8 routines are an
> emulated or synthesized data type.  in the test I did on our 7.0.2 server I
> notice about a 25-30% decrease in performance when using complex joins on
> tables containing referential keys, primary keys all in the int8 data type.
> 
> This might be something to think about as well.

Thanks.  Because of these and other comments people have made, I've gone back
to using a flat_file-with-server approach instead of adding a table to my
postgres DB.  While an int4 *might* work, it doesn't handle the "worst-case"
scenario (which is up around 15 billion values).

Thanks to everyone for your comments and suggestions!

--
Steve Wampler-  SOLIS Project, National Solar Observatory
swampler@noao.edu



view thread (11+ messages)  latest in thread

Message-ID: <3A117A15.6A247634@noao.edu>
Permalink:  ../3A117A15.6A247634@noao.edu/
Also on:    postgresql.org/message-id/3A117A15.6A247634@noao.edu

 · 

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: swampler@noao.edu, tswan@olemiss.edu, michael_teter@yahoo.com, poet@linuxports.com
  Subject: Re: Using a postgres table to maintain unique id?
  In-Reply-To: <3A117A15.6A247634@noao.edu>
  References: <5.0.0.25.0.20001114113001.00aad5f8@sunset.backbone.olemiss.edu> <3A117A15.6A247634@noao.edu>

* 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