Re: Enforcing serial uniqueness?

From: Alban Hertroys <alban(at)magproductions(dot)nl>
To: Csaba Nagy <nagy(at)ecircle-ag(dot)com>
Cc: Postgres general mailing list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Enforcing serial uniqueness?
Date: 2006-03-22 12:28:17
Message-ID: 442142E1.7090903@magproductions.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Csaba Nagy wrote:
>>That way they really can't touch the sequence; otherwise they still
>>could call nextval multiple times erroneously (people do that...). It
>>doesn't matter much to the sequence, of course... It just leaves the
>>ugly gaps out :P
>
>
> The sequence facility was NOT designed with no-gap sequencing in mind,
> but with good parallel performance in mind.

I didn't suggest anything of the kind. I was just suggesting a (IMO)
cleaner way to allow access to the sequence, so that the users of the
OP's database don't make too much of a mess of it. As I said, it won't
matter much to the sequence. It's just a matter of wanting to do things
the 'proper' way.

--
Alban Hertroys
alban(at)magproductions(dot)nl

magproductions b.v.

T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede

// Integrate Your World //

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Csaba Nagy 2006-03-22 12:38:31 Re: Enforcing serial uniqueness?
Previous Message Terry Lee Tucker 2006-03-22 11:47:47 Re: Updating a primary key