Re: primary key and existing unique fields

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Dawid Kuroczko <qnex42(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: primary key and existing unique fields
Date: 2004-10-27 13:55:34
Message-ID: 20041027135534.GC3160@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Oct 27, 2004 at 00:10:27 +0200,
Dawid Kuroczko <qnex42(at)gmail(dot)com> wrote:
> 3. If you'll need things like "last 50 keys", you can SELECT * FROM
> foo ORDER BY yourserialkey DESC LIMIT 50;

You really shouldn't be doing that if you are using sequences to generate
the key. Sequences are just guarenteed to return unique values, not to
return them in order. Because groups of sequences can be allocated to
a backend at once depending on a setting settable by a client, you can
get assignments out of order. Also for overlapping transactions what
the application means by the last 50 entries may not match what you
get when you get the 50 highest serial values.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Carlos Oliva 2004-10-27 14:05:48 Re: Changing access permissions without re-starting the database
Previous Message Michael Glaesemann 2004-10-27 13:27:27 Re: Changing access permissions without re-starting the database