| From: | Jorge Godoy <jgodoy(at)gmail(dot)com> |
|---|---|
| To: | snacktime <snacktime(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: alternative to using a sequence |
| Date: | 2006-08-26 10:42:19 |
| Message-ID: | 87wt8vvkvo.fsf@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
snacktime <snacktime(at)gmail(dot)com> writes:
> I have an application that processes financial transactions. Each of
> these transactions needs to be sent with a sequence number. It starts
> at 1 and resets to 1 once it hits 8000. I'm trying to think of the
> most elegant solution without having to create a sequence for each
> user (there are hundreds). There is a table that holds the
> configuration parameters for each merchant, so a field in that table
> to hold the sequence number would be ideal. In the past I've used
> sequences as well as just a field which I query then update. Any
> other ideas?
Take a look at http://www.varlena.com/GeneralBits/
There are some ideas there. Of course, gapless sequences perform a bit worse
than sequences. There was this discussion here on the ML last week as well,
so in the archives you'll find even more things to think.
--
Jorge Godoy <jgodoy(at)gmail(dot)com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Purusothaman A | 2006-08-26 10:47:27 | Win2000 professional / Error message while installing PostgreSQL "Failed to create process: 2! ". |
| Previous Message | Ragnar | 2006-08-26 09:52:47 | Re: speeding up big query lookup |