Re: Primary Key Increment Doesn't Seem Correct Under Table Partition

From: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
To: Yan Cheng Cheok <yccheok(at)yahoo(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Primary Key Increment Doesn't Seem Correct Under Table Partition
Date: 2010-01-26 10:36:07
Message-ID: 20E1D1DD-DA3C-44D4-8A4E-9FB924A49E9C@solfertje.student.utwente.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 26 Jan 2010, at 11:00, Yan Cheng Cheok wrote:

> However, whenever I insert row into measurement table, I realize its primary key value is going from 2, 4, 6, 8, 10...
>
> May I know how can I prevent this?

Apparently nextval on that sequence gets called multiple times in your queries.

> Also, is it necessary to create index for measurement_id found in measurement's child table? I am concern on the read speed.

Serials don't create indexes, only a sequence. Primary keys create indexes (to guarantee uniqueness) - foreign keys do not.
So yes, you want an index on that column in the child table.

Alban Hertroys

--
Screwing up is the best way to attach something to the ceiling.

!DSPAM:737,4b5ec59910605107914066!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message A. Kretschmer 2010-01-26 12:30:54 Re: Correct Concept On Table Partition
Previous Message Yan Cheng Cheok 2010-01-26 10:08:05 Correct Concept On Table Partition