Concurrency issue under very heay loads

Поиск
Список
Период
Сортировка
От Raji Sridar (raji)
Тема Concurrency issue under very heay loads
Дата
Msg-id 69520586F2CA1444B3F6BE05187B9ABAAC97D4@xmb-sjc-226.amer.cisco.com
обсуждение исходный текст
Ответы Re: Concurrency issue under very heay loads  (Greenhorn <user.postgresql@gmail.com>)
Re: Concurrency issue under very heay loads  (John R Pierce <pierce@hogranch.com>)
Re: [PERFORM] Concurrency issue under very heay loads  (Scott Marlowe <scott.marlowe@gmail.com>)
Re: [PERFORM] Concurrency issue under very heay loads  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Re: Concurrency issue under very heay loads  (Bill Moran <wmoran@potentialtech.com>)
Re: Concurrency issue under very heay loads  (Greg Smith <gsmith@gregsmith.com>)
Re: [PERFORM] Concurrency issue under very heay loads  ("Haszlakiewicz, Eric" <EHASZLA@transunion.com>)
Список 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 по дате отправления:

Предыдущее
От: Arndt Lehmann
Дата:
Сообщение: Re: best practice transitioning from one datatype to another
Следующее
От: "ramasubramanian"
Дата:
Сообщение: Re: [PERFORM] Concurrency issue under very heay loads