pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: bigserial vs serial - which one I'd have to use?
Date: 27 Jan 2003 13:55:04 -0600
Message-ID: <1043697304.9899.60.camel@haggis> (raw)
In-Reply-To: <200301271133.37738.josh@agliodbs.com>
References: <1043616281.829.38.camel@maci>
	<200301271133.37738.josh@agliodbs.com>

On Mon, 2003-01-27 at 13:33, Josh Berkus wrote:
> Medve,
> 
> > Have you got any data (ie in percentage) of around how much more CPU
> > work needed with the bigserial type in the queries?
> > 
> > I have a log database with 100million records (the biggest table
> > contains 65million records) and I use bigserial data type as primary key
> > now. The primary key looks this way: YYYYMMDD1xxxxxxx where the first 8
> > numbers are the date, and the x's are the record sequence number on that
> > day. This way the records are in ascendant order. Almost all of the
> > queries contains date constraints (PK like 'YYYYMMDD%'). I'd like to
> > know if I do it in a stupid way or not. I'm not a DBA expert so every
> > idea are welcome. If you need more information about the
> > hardware/software environment, the DB structure then I'll post them.
> 
> Given that structure, I'd personally create a table with a 2-column primary 
> key, one column of type DATE and one SERIAL column.  Alternately, if you find 
> the conversion of DATE to char for output purposes really slows things down, 
> one column of INT and one of SERIAL.    Either way, the two columns together 
> make up the primary key.
> 
> I would definitely suggest avoiting the temptation to do this as a single 
> column of type CHAR().   That would be vastly more costly than either 
> strategy mentioned above:
> 
> DATE + SERIAL (INT) = 8 bytes

Ah, cool.  I thought DATE was 8 bytes.  Should have RTFM, of course.

> INT + SERIAL (INT) = 8 bytes
>
> CHAR(16) = 18 bytes

-- 
+---------------------------------------------------------------+
| Ron Johnson, Jr.        mailto:ron.l.johnson@cox.net          |
| Jefferson, LA  USA      http://members.cox.net/ron.l.johnson  |
|                                                               |
| "Fear the Penguin!!"                                          |
+---------------------------------------------------------------+




view thread (4+ messages)

Message-ID: <1043697304.9899.60.camel@haggis>
Permalink:  ../1043697304.9899.60.camel@haggis/
Also on:    postgresql.org/message-id/1043697304.9899.60.camel@haggis

 · 

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-performance@postgresql.org
  Cc: ron.l.johnson@cox.net
  Subject: Re: bigserial vs serial - which one I'd have to use?
  In-Reply-To: <1043697304.9899.60.camel@haggis>
  References: <1043616281.829.38.camel@maci> <200301271133.37738.josh@agliodbs.com> <1043697304.9899.60.camel@haggis>

* 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