Re: [PERFORM] Concurrency issue under very heay loads - Mailing list pgsql-general

From Albe Laurenz
Subject Re: [PERFORM] Concurrency issue under very heay loads
Date
Msg-id D960CB61B694CF459DCFB4B0128514C203937E41@exadv11.host.magwien.gv.at
Whole thread Raw
In response to Concurrency issue under very heay loads  ("Raji Sridar (raji)" <raji@cisco.com>)
Responses Re: [PERFORM] Concurrency issue under very heay loads  (Allan Kamau <kamauallan@gmail.com>)
List pgsql-general
Raji Sridar wrote:
> 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.

Please show us your code!

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: Rafael Martinez
Date:
Subject: Problems with 8.4, FLOAT8PASSBYVAL and x86_64 GNU/Linux
Next
From: "Massa, Harald Armin"
Date:
Subject: overwrite the encoding of a database