| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Raji Sridar \(raji\) *EXTERN*" <raji(at)cisco(dot)com>, <pgsql-general(at)postgresql(dot)org>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: [PERFORM] Concurrency issue under very heay loads |
| Date: | 2009-07-16 09:15:24 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C203937E41@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arndt Lehmann | 2009-07-16 09:22:26 | Re: best practice transitioning from one datatype to another |
| Previous Message | Rafael Martinez | 2009-07-16 09:14:48 | Problems with 8.4, FLOAT8PASSBYVAL and x86_64 GNU/Linux |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ning | 2009-07-16 09:30:00 | Re: Repeated Query is much slower in PostgreSQL8.2.4 than DB2 9.1 |
| Previous Message | Andres Freund | 2009-07-16 07:45:45 | Re: Repeated Query is much slower in PostgreSQL8.2.4 than DB2 9.1 |