| From: | Greenhorn <user(dot)postgresql(at)gmail(dot)com> |
|---|---|
| To: | "Raji Sridar (raji)" <raji(at)cisco(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Concurrency issue under very heay loads |
| Date: | 2009-07-16 05:30:53 |
| Message-ID: | ddcb1c340907152230k7130c305ydb12296d811ccf9e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
2009/7/16 Raji Sridar (raji) <raji(at)cisco(dot)com>:
> 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
You'll not have this problem if you use serial type.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2009-07-16 05:34:58 | Re: Concurrency issue under very heay loads |
| Previous Message | ramasubramanian | 2009-07-16 05:19:17 | Re: [PERFORM] Concurrency issue under very heay loads |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2009-07-16 05:34:58 | Re: Concurrency issue under very heay loads |
| Previous Message | Marc Cousin | 2009-07-16 05:20:18 | Re: Very big insert/join performance problem (bacula) |