Concurrency issue under very heay loads - Mailing list pgsql-general

Hi,
 
We use a typical counter within a transaction to generate order sequence number and update the next sequence number. This is a simple next counter - nothing fancy about it.  When multiple clients are concurrently accessing this table and updating it, under extermely heavy loads in the system (stress testing), we find that the same order number is being generated for multiple clients. Could this be a bug? Is there a workaround? Please let me know.
 
Thanks
Raji

pgsql-general by date:

Previous
From: Arndt Lehmann
Date:
Subject: Re: best practice transitioning from one datatype to another
Next
From: "ramasubramanian"
Date:
Subject: Re: [PERFORM] Concurrency issue under very heay loads