From: | Markus Espenhain <espenhain(at)etes(dot)de> |
---|---|
To: | Postgres <pgsql-admin(at)postgresql(dot)org> |
Subject: | Problem with Sequences |
Date: | 2003-09-12 11:30:22 |
Message-ID: | 20030912113022.GA8859@intranet.etes.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello all,
I am new here...
I have a Problem by one of our Applications.
The Frontend ist an Access-Application who connects through ODBC to the postgres-database (7.3.2).
Two of the three Applications works fine. The other have possibly an Problem with Sequences.
The Problem is the folowing:
On user who works with the Database create an new record and save this.
Here the record becomes an ID and another Number from an two sequences.
One other user ist in this moment working with the database and create an new record, too.
Now he becomes in some circumstances the same ID like the first saved record from the other user with the effect, that the other record is nolong in the database.
Is this problem possible?
How the sequences where build (processlist)?
Can an extremly high load of the server (2.0-5.0) can create such Problems?
Thanks for ideas and help...
cu
Markus
--
Markus Espenhain Fon: +49 (7 11) 48 90 83 - 0
ETES - EDV-Systemhaus GbR Fax: +49 (7 11) 48 90 83 - 50
Libanonstrasse 58 A * D-70184 Stuttgart Web: http://www.etes.de
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2003-09-12 13:32:55 | Re: Row locking during UPDATE |
Previous Message | suresh prasanna | 2003-09-12 08:58:00 | unsubsribe |