From: Medve Gabor <eire@enternet.hu>
To: pgsql-performance@postgresql.org
Subject: bigserial vs serial - which one I'd have to use?
Date: 26 Jan 2003 22:24:41 +0100
Message-ID: <1043616281.829.38.camel@maci> (raw)
Hi all,
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.
Thanks in advance for your help.
Gabor
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: eire@enternet.hu
Subject: Re: bigserial vs serial - which one I'd have to use?
In-Reply-To: <1043616281.829.38.camel@maci>
References: <1043616281.829.38.camel@maci>
* 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