Skip site navigation (1) Skip section navigation (2)

Concurrency issue under very heay loads

From: "Raji Sridar (raji)" <raji(at)cisco(dot)com>
To: <pgsql-general(at)postgresql(dot)org>, <pgsql-performance(at)postgresql(dot)org>
Subject: Concurrency issue under very heay loads
Date: 2009-07-16 04:59:41
Message-ID: 69520586F2CA1444B3F6BE05187B9ABAAC97D4@xmb-sjc-226.amer.cisco.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-performance
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

Responses

pgsql-performance by date

Next:From: ramasubramanianDate: 2009-07-16 05:19:17
Subject: Re: [PERFORM] Concurrency issue under very heay loads
Previous:From: Justin PittsDate: 2009-07-16 02:17:27
Subject: Re: cluster index on a table

pgsql-general by date

Next:From: ramasubramanianDate: 2009-07-16 05:19:17
Subject: Re: [PERFORM] Concurrency issue under very heay loads
Previous:From: Bruce MomjianDate: 2009-07-16 04:28:47
Subject: Re: [GENERAL] pg_migrator not setting values of sequences?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group