Re: [INTERFACES] locking on database updates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gary Stainburn <gary(dot)stainburn(at)ringways(dot)co(dot)uk>
Cc: "'Pgsql Interfaces'" <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: Re: [INTERFACES] locking on database updates
Date: 1999-12-07 01:14:21
Message-ID: 20458.944529261@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Gary Stainburn <gary(dot)stainburn(at)ringways(dot)co(dot)uk> writes:
> My question is this. Is there a safe way of retrieving the next
> number from the parameter table in such a way that the same number
> cannot be retrieved twice.

Use a SEQUENCE object for each "parameter table". This gives you
a well-tested, efficient generator mechanism. It may be "auto
generated" but you do have the option of resetting the sequence's
nextval and so forth, so I don't see that there is a good reason
to build a SEQUENCE substitute by hand.

regards, tom lane

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Joseph Shraibman 1999-12-07 02:59:42 Re: [INTERFACES] locking on database updates
Previous Message Rich Shepard 1999-12-06 18:20:14 Re: [INTERFACES] locking on database updates